"Ralf Canis" <rc / duria.de> wrote in message
news:6kvqlt8jk0527bfr15e8fclh7tc60h5vd3 / 4ax.com...

> under Windows (1.6.4 install-shield version) but work fine with the Linux
> version.
>
> Looks like a call to recv on a nonblocking socket WITHOUT any data to read
> causes this "bug".


> - Anybody can confirm this?
> - Does a method exist to check if there is anything in the
>   input queue without calling recv? (ok, I can catch this exception but
>   there has to be a better solution)

I'm not sure if this is related, but it is getting increasingly late.
However, I was looking at some Ruby telnet server source that used to be
working, and suddenly didn't. I may just be a bug in my code, but it appears
like when the telnet client disconnects, receive is no longer blocking, but
the disconnect is  also not detected. I believe I tested on 1.6.1 windows
install distribution last time. Now on windows 1.6.4 I can't get it working.

Mikkel