Up to now I always used blocking sockets for my client/server communication, but from time to time I end up having some deadlocks when the server is stopping. So I wish to switch to non blocking sockets.
The client/server protocol is ASN.1 based. I use ASN1_d2i_bio and ASN1_i2d_bio to exchange datas.
The BIO is created like this 'BIO_set_ssl(ssl_bio, ssl, BIO_CLOSE)'
and the SSL is created like this 'SSL_set_fd(ssl, connection)'
'connection' being the socket returned by 'accept'.
Will 'BIO_f_ssl' implementation or ASN1_d2i_bio be able to handle SSL_ERROR_WANT_READ or SSL_ERROR_WANT_WRITE by itself ?
If not, how do I do this ?
-- Frédéric Giudicelli http://www.newpki.org ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
