From: rakaur <rakaur@...>
Date: 2006-02-14T08:43:26+09:00
Subject: Re: nonblocking sockets, select, & OpenSSL

My code at the previous URL has been updated, as it seems I've found
the culprit.

SSLSocket#read doesn't behave as it should. If you specify a size (as I
did earlier, 8192) it blocks until that many bytes have been read,
instead of reading up to a maximum of that many bytes as TCPSocket#recv
does.

Is there any obvious way to get around this other than reading it in
one character at a time? This would use significantly more CPU, as it
results in one system call per byte instead of one system call per
maximum of 8192 bytes.