> So is the SSL_read() blocking or non-blocking. I always thought it was
> blocking until yesterday when
>
> a) I saw that the structure ends up pointing at the ssl3_read() (if meth is
> ssl3_...) that uses a BIO if you set one (rbio and wbio) and I believe that
> yields a non-blocking func.
>
> b) this morning when some one (Andrew?) here said that they were
> non-blocking by default.
>
> Unfortunately some one else Richard (i think) disagree's.
>
> What if you (in Win32) do the inital connect Async and then do SSL_connect
> on that (like some of the old demos (cli.c & srv.c)? Does that make it
> non-blocking as you are doing an asyncselect on the socket?
>
> who's right?
>
You can always change blocking mode via the ioctl() (in Windows
ioctlsocket()) call.
I use non-blocking mode in windows because unlike Unix there is no
safe method to cancel a blocking function in Windows.
Jeffrey Altman * Sr.Software Designer * Kermit-95 for Win32 and OS/2
The Kermit Project * Columbia University
612 West 115th St #716 * New York, NY * 10025
http://www.kermit-project.org/k95.html * [EMAIL PROTECTED]
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
