Hi, Does the SSL layer have its own read buffering? Our application has a standard non-blocking socket loop where we wait for a read event, read 8k, and go back to wait for more. If we have more than 8k then we have multiple events until the data is complete. On extending the application to use OpenSSL, this seemed to work OK during testing, replacing the socket read with SSL_read. But now I have a case where, from the debug output, it seems that the SSL_read reads all available data, but only returns the 8k requested. As a result when we return to wait, there is no read event to trigger any further calls to SSL_read, as all the data has already been read. This only seems to be the case on NT (so far), and in certain (unclear) circumstances. This is not mentioned in the SSL_read man page as ar as I can see. Thanks for any help, G. ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
