From: Nikos Mavrogiannopoulos Date: Tue, 13 Sep 2011 20:03:36 +0000 (+0200) Subject: clarified format of sequence number in gnutls_record_recv_seq. X-Git-Tag: gnutls_3_0_3~24 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=d68a6257d5a4bf6b58d2561e111ce0726f38cfec;p=thirdparty%2Fgnutls.git clarified format of sequence number in gnutls_record_recv_seq. --- diff --git a/lib/gnutls_buffers.c b/lib/gnutls_buffers.c index 4f946f4445..b93d4c4532 100644 --- a/lib/gnutls_buffers.c +++ b/lib/gnutls_buffers.c @@ -21,9 +21,8 @@ * */ -/* This is the only file that uses the berkeley sockets API. - * - * Also holds all the buffering code used in gnutls. +/* + * This file holds all the buffering code used in gnutls. * The buffering code works as: * * RECORD LAYER: diff --git a/lib/gnutls_record.c b/lib/gnutls_record.c index 7ef94cc5c3..874099f3df 100644 --- a/lib/gnutls_record.c +++ b/lib/gnutls_record.c @@ -1247,8 +1247,9 @@ gnutls_record_recv (gnutls_session_t session, void *data, size_t data_size) * This function is the same as gnutls_record_recv(), except that * it returns in addition to data, the sequence number of the data. * This is useful in DTLS where record packets might be received - * out-of-order. The returned 8-byte sequence number should be - * treated as a unique message identification. + * out-of-order. The returned 8-byte sequence number is an + * integer in big-endian format and should be + * treated as a unique message identification. * * Returns: The number of bytes received and zero on EOF. A negative * error code is returned in case of an error. The number of bytes