The Streaming API is currently configured to send a keep-alive newline every 30 seconds. If you don't receive any data or the keep-alive in perhaps 60 or 90 seconds, you should drop and reconnect. The only case where what you observed should happen is if a load balancer restarts. I don't think this happened at 4pm -- rather, there was a Hosebird deploy at around this time. If anything, you should have received an HTTP error code, a TCP RST or TCP CLOSE at this time.
If you were connecting twice with the same username, your earlier connection may have been dropped due to duplication. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Mon, Apr 19, 2010 at 8:28 PM, Amitab <hiamita...@gmail.com> wrote: > Hi, > > There was a thread about this before in which Twitter folks mentioned > that there was a problem with the load balancers. > > This happened at about 4pm PDT. The streaming API didnt send anything > and neither terminated the connection. I restarted my streaming and it > started working again. I have two streaming sessions, one from my host > machine and another from my test machine, and both sessions had the > same issue at the same time. > > Does Twitter recommend that we break the connection if no data arrives > in some time and then restart it? > > /Amitab > > Twaller.com(@mytwaller) > > > -- > Subscription settings: > http://groups.google.com/group/twitter-development-talk/subscribe?hl=en >
