[gnutls-dev] gnutls_record_send/recv documentation inconsistencies

[Tim Kosse]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Currently, the documentation for both gnutls_record_recv as well as
gnutls_record_send contains this paragraph:

" * If EINTR is returned by the internal push function (the default is
  * @code{recv()}) then GNUTLS_E_INTERRUPTED will be returned. If
  * GNUTLS_E_INTERRUPTED or GNUTLS_E_AGAIN is returned, you must call
  * this function again, with the same parameters; alternatively you
  * could provide a NULL pointer for data, and 0 for
  * size. cf. @code{gnutls_record_get_direction()}."

Actually, both the push and the pull functions can be invoked by a call
to either of the two functions.

In the case of gnutls_record_recv, calling this function with NULL data
and/or 0 size, GNUTLS_E_INVALID_REQUEST is returned, even if it failed
with GNUTLS_E_AGAIN before.

Furthermore, the requirement to "call this function again, with the same
parameters" does not hold for gnutls_record_recv either.

Tim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFUNTI8N9+lcqiUkURAo6iAJ9Zri5OOpCz5dPf4H3ScRcYmbcX/wCfSV9y
nAUWQm/ddMvIg3A5WViP0n4=
=Qip0
-----END PGP SIGNATURE-----