On Jul 19, 2007, at 9:45 PM, Jim Marshall wrote:
Jim Marshall wrote:
David Schwartz wrote:
OpenSSL tries to make SSL connections act like regular TCP
connections. This
is exactly what TCP does. So your application would have this
exact same
problem with or without OpenSSL. As such, how can you blame it on
OpenSSL?
Not to beat a dead horse, but I forgot to mention that the
application does work "properly" when performing the same
operations on non-SSL connections. In other-words if I use telnet
to connect to the server on the non-SSL port and type nothing in
the console and then have a second client connect (to either the
non-SSL or the SSL port) and make a valid request, the server
responds properly. The telnet session is still connected, but we
are not blocked from handling other requests. The WEBs code uses
the socket 'select' mechanism which I presume plays a role in this
working. I do not understand why this same mechanism fails when we
use SSL.
The 'same mechanism' is not failing when you use openssl. You're
just not doing it right. If you set your SSL sockets to non-blocking
and include any SSL socket 'want-read' and 'want-write' in your
selects everything will work. There is no magic bullet though. SSL
is more complex than telnet and you have to deal with that complexity.
Jim
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager [EMAIL PROTECTED]
