There is aexmple implemtation of usage ofbio_pairs in ssltest.c file includedwith the ssl distribution. This should give you a goodidea about how to use them properly.I too took that sameimplemetion from ssltest.cand wrapedit ina class for my IOCP serverwithout too much of a trouble.
Regards,
Terry
I ran into same problem a while ago. I had a blocking server, waiting
for client to connect. I had non-blocking client connected to server, It
never pass SSL_connect(). I changed non-blocking to blocking I/O BEFORE
I called SSL_connect(). It worked fined. It seem to me you need to using
hello Thao
Thank you for trying but no, this does not help.
If you want to build a single threaded scalable server using nonblocking
i/o, you need to use exclusively nonblocking i/o. You can't conveniently
block on one connection while it sorts itself out, as you put the other
connections
15:43
To: openssl-users@openssl.org
Subject: RE: openssl with non-blocking comms
hello Thao
Thank you for trying but no, this does not help.
If you want to build a single threaded scalable server using nonblocking
i/o, you need to use exclusively nonblocking i/o. You can't conveniently
block
On Tue, Jan 30, 2007, Dinh, Thao V CIV NSWCDD, K72 wrote:
Terry
I ran into same problem a while ago. I had a blocking server, waiting
for client to connect. I had non-blocking client connected to server, It
never pass SSL_connect(). I changed non-blocking to blocking I/O BEFORE
I called
When you say that a connection 'gets accepted normally', does
that mean you do the following:
1) accept
2) use fcntl to set the connection to non-blocking
3) gets a new SSL/BIO to use the connection
4) call SSL_accept
I found that step 2 has to come after step 4. At this point, I am
assuming
