On Thu, Jun 22, 2006 at 07:35:15AM -0700, 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*.
This is no longer a productive use of the list's time. Please redirect
to a suitable system programming list. From a pragmatic viewpoint
(doing non-blocking I/O on blocking sockets right is subtle, requires
care, and some not always applicable pre-conditions) I agree with you,
but your zeal is excessive. Just because it is difficult, does not mean
that OpenSSL should flagrantly make it more difficult.
Ideally behind the scenes, while we argue philosophy, someone on the
OpenSSL team is looking at the code... Perhaps they will make more
progress if we now desist from this discussion.
--
Viktor.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [email protected]
Automated List Manager [EMAIL PROTECTED]
