Hello everybody !
David Schwartz wrote:
Since 'select' does not guarantee that a subsequent read operation won't
block (since it can't even know what operation that's going to be), the
subsequent read operation (which was 'SSL_read') blocked. That's because
SSL_read blocks for *application* *data* while 'select' checks for *any*
*data*.
Can I play ? :)
I'm wondering if it would not be highly appropriate to have an
'SSL_select' call defined by OpenSSL to have all operations on sockets
fully encapsulated and allow to reach the desired behaviour without
short-circuiting the layer approach... (it would provide similar
behaviour as classical select on plain sockets with regard to
application data).
Now I apologize if this thought is trivially appropriate or trivially
inappropriate - I missed the beginning of this thread to be honest.
Goodbye everybody !
--
Alain Damiral,
I hope this message makes me look like a very intelligent person
Université Catholique de Louvain - student
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [email protected]
Automated List Manager [EMAIL PROTECTED]
