diff options
author | Richard Levitte <levitte@openssl.org> | 2000-09-21 06:46:15 +0000 |
---|---|---|
committer | Richard Levitte <levitte@openssl.org> | 2000-09-21 06:46:15 +0000 |
commit | c19b6c922a6575974455404be3c1409de60fb1eb (patch) | |
tree | 9028e11834ce68083ad559adaf34f83c4e12a7e7 /doc/ssl/SSL_write.pod | |
parent | c5f8bbbc0b94f3ec3f3f8f2aabbe3cc81f7b8158 (diff) |
Clarifications and new documents.
Submitted by Lutz Jaenicke <Lutz.Jaenicke@aet.TU-Cottbus.DE>
Diffstat (limited to 'doc/ssl/SSL_write.pod')
-rw-r--r-- | doc/ssl/SSL_write.pod | 12 |
1 files changed, 11 insertions, 1 deletions
diff --git a/doc/ssl/SSL_write.pod b/doc/ssl/SSL_write.pod index b086258e82..0a1adaba73 100644 --- a/doc/ssl/SSL_write.pod +++ b/doc/ssl/SSL_write.pod @@ -13,7 +13,11 @@ SSL_read - write bytes to a TLS/SSL connection. =head1 DESCRIPTION SSL_write() writes B<num> bytes from the buffer B<buf> into the specified -B<ssl>. If necessary, SSL_write() will negotiate a TLS/SSL session, if +B<ssl> connection. + +=head1 NOTES + +If necessary, SSL_write() will negotiate a TLS/SSL session, if not already explicitly performed by SSL_connect() or SSL_accept(). If the peer requests a re-negotiation, it will be performed transparently during the SSL_write() operation. The behaviour of SSL_write() depends on the @@ -34,6 +38,12 @@ non-blocking socket, nothing is to be done, but select() can be used to check for the required condition. When using a buffering BIO, like a BIO pair, data must be written into or retrieved out of the BIO before being able to continue. +=head1 IMPORTANT + +When an SSL_write() operation has to be repeated because of +B<SSL_ERROR_WANT_READ> or B<SSL_ERROR_WANT_WRITE>, it must be repeated +with the same arguments. + =head1 RETURN VALUES The following return values can occur: |