> David Schwartz wrote: > > Which is pretty much the same as every other operation. If you > > call 'send' > > or 'write' on a blocking TCP socket, and you get a zero return, > > does that > > mean the data has been sent? No. It means the data is queued > > and the send is > > in progress. If you call 'shutdown' on a blocking socket and get a zero > > return, does that mean the connection has finished shutting down? No. It > > means the shutdown is in progress.
> I take point with DS on this single aspect. Please name the > implementation of send() or write() that uses a zero return code to mean > "the data is queued and the send is in progress". I know of no such > implementation. Sorry, I meant non-error. Not zero. That should read, "If you call 'send' or 'write' on a blocking TCP socket, and you get a non-error return, ..." > A non-zero positive error return is always used to indicate that > situation in all implementations of send() and write() I have come across. Correct, zero is failure for send/write. > The interpretation of what zero means in respect of SSL_shutdown() is a > matter for the OpenSSL documentation to clarify. > > I myself can not see the parallel that DS can see in respect of the > send/write APIs - so please ignore this confusion DS introduces. My apologies for the mistake. I hope I didn't confuse anybody. DS ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
