On Thu, Sep 13, 2007, Loukas Stoumbos wrote: > > > I appreciate the reply but perhaps someone can provide some insight. Looking > at the man page it says this. > > BIO_set_nbio() sets the non blocking I/O flag to n. If n is zero then > blocking I/O is set. If n is 1 then non blocking I/O is set. Blocking I/O is > the default. The call to BIO_set_nbio() should be made before the connection > is established because non blocking I/O is set during the connect process. > > What does it mean that the non blocking I/O is set during the connect > process? Does it change the socket into non blocking afterwards or does it > revert back to blocking? >
Non blocking is set when the socket is created, before the connect process. So the actual connect takes place with non-blocking I/O set and it may be necessary (depending on retry condition) to wait for a connect event. Non blocking I/O stays set and it does not revert to blocking later. Steve. -- Dr Stephen N. Henson. Email, S/MIME and PGP keys: see homepage OpenSSL project core developer and freelance consultant. Funding needed! Details on homepage. Homepage: http://www.drh-consultancy.demon.co.uk ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
