Ben Laurie [mailto:email@example.com] wrote:
> The point is that in the standard case, a byte on the network is a byte
> in the application, so you either get a byte or you time out in the
> specified time.
> In the SSL case, you could neither get a byte nor time out, at the
> application layer, until much, much later than you thought you specified.
> This seems broken to me, and POLA would suggest I'm right (i.e. if I say
> time out in 1 second, I'll be pretty astonished when that turns into a
I would agree if we were talking about a timeout that was explicitly set on
the SSL layer. But if I set a timeout on a socket, I expect it to apply to
the individual low-level socket operations, not to the higher level SSL