I am completely & finally confused. Anyways, a fix which i provided initially doesn't deals with timeouts, just picks the right byte. And it works for me. ;) 2010/1/15 Andreas Raab <andreas.raab@gmx.de>:

Andreas Raab wrote:

...

Andreas Raab wrote:

...

Igor Stasenko wrote:

...

" the above should endup with timeout exception , but following one should hang indefinitely"

Absolutely not. Read the comment on shouldSignal:

   "If shouldSignal is enabled the Socket Exceptions    ConnectionClosed and ConnectionTimedOut"

And I guess I should read more carefully, too :-) In any case, timeouts *are* handled via #timeout: and that makes good sense.

(last response to my own post :-)

And of course, the easy to do what you're trying to do is to change:

shouldTimeout        ^timeout > 0 and:[shouldSignal]

This would suppress all timeouts unless shouldSignal is true. BTW, I've never seen a case where I've been using a non-signaling socket stream. Does that case even exist?

I guess no.

Cheers,  - Andreas

-- Best regards, Igor Stasenko AKA sig.