On Fri, Feb 07, 2003 at 12:15:31PM -0800, David Schwartz wrote: > On Fri, 7 Feb 2003 20:42:50 +0100, Jasper Spit wrote:
>> My point was to make clear that your statement that 'it is almost always >> an error to use select() with non blocking sockets' is simply not true. >> I think that might be relevant to other openssl users. > I stand by my point until and unless you can find some guarantee > that what 'select' tells you is true now will continue to be true in > the future when you get around to calling whatever I/O function you > were planning to call. So you really meant "It is almost always an error to use select() with *blocking* sockets". [...] > If you are willing to block, there is no reason to call 'select'. If > you cannot block, you cannot do I/O on blocking sockets. This way around, this especially true when using the OpenSSL API, where a single function call such as SSL_read() or SSL_write() can start multiple socket-level I/O operations. (In a typical case, SSL_read() will first read the record header, then the actual data. In more complicated cases, SSL_read() or SSL_write() may have to finish a complete TLS/SSL handshake before even starting with the application data.) -- Bodo Möller <[EMAIL PROTECTED]> PGP http://www.informatik.tu-darmstadt.de/TI/Mitarbeiter/moeller/0x36d2c658.html * TU Darmstadt, Theoretische Informatik, Alexanderstr. 10, D-64283 Darmstadt * Tel. +49-6151-16-6628, Fax +49-6151-16-6036 ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
