From: Roger Pack <rogerpack2005@...>
Date: 2009-05-20T21:42:55+09:00
Subject: Re: Detect TCPSocket interruptions/disappearance

> In such a case the code simply hangs on the gets request within the
> loop and never returns.

Odd. If the socket closes then gets should return nil

So in this case the only way you know it closed is that...it goes away 
without notifying you?
If that's the case then some type of periodic liveness ping is the only 
way, I think (as Brian noted).
-=r
-- 
Posted via http://www.ruby-forum.com/.