On Mon, Apr 24, 2000 at 11:11:11PM -0400, David wrote:
> My understanding of the typical use of OpenSSL is that blocking functions
> such as SSL_connect(), SSL_read() and SSL_write() are used, with each
> function handling a number of negotiation interactions.
>
> For my non-SSL work I use nonblocking sockets with select() to handle a
> number of web interactions simultaneously, and it would seem that the
> standard OpenSSL approach is not compatible with this functionality.
It's possible to use non-blocking sockets with OpenSSL. Things are a
bit more complicate than when using non-blocking sockets without
SSL/TLS, though, because reading SSL data may require sending network
data, and writing SSL data may require receiving network data, in
addition to the obvious data transfers. OpenSSL can handle
non-blocking sockets without problems (just switch the sockets to
non-blocking mode, you don't have to tell the library about this); for
handling this correctly in your program, read the SSL_get_error() manual
page.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
