From: Walle Wallen on 24 Jun 2010 12:14 It still happens, but very rarely... The bot kicks in again if I write anything in the window($stdin). Does anyone have any thoughts on this? //Walle -- Posted via http://www.ruby-forum.com/.
From: Roger Pack on 24 Jun 2010 13:57 Walle Wallen wrote: > It still happens, but very rarely... The bot kicks in again if I write > anything in the window($stdin). > Does anyone have any thoughts on this? Yeah I think it's a generic "problem" of TCP. If the other side has closed the socket (or died, or been rebooted), and you never write anything to the socket, you will never learn it is closed until the next time you write something. http://en.wikibooks.org/wiki/Ruby_Programming/Reference/Objects/Socket#keepalive -- Posted via http://www.ruby-forum.com/.
From: Walle Wallen on 25 Jun 2010 05:10 Roger Pack wrote: > Walle Wallen wrote: >> It still happens, but very rarely... The bot kicks in again if I write >> anything in the window($stdin). >> Does anyone have any thoughts on this? > > Yeah I think it's a generic "problem" of TCP. If the other side has > closed the socket (or died, or been rebooted), and you never write > anything to the socket, you will never learn it is closed until the next > time you write something. > > http://en.wikibooks.org/wiki/Ruby_Programming/Reference/Objects/Socket#keepalive Oh, okey. Thank you for the insight. //Walle -- Posted via http://www.ruby-forum.com/.
|
Pages: 1 Prev: Count substrings in string, scan too slow Next: [ANN] Money 3.0.4 |