The best practices guide (or some doc) explains the streaming connections
have heartbeats every 60 seconds or so.  You should listen for them.  If you
don't hear one for 90 seconds, drop the connection and reconnect.

On Sun, Jan 2, 2011 at 7:48 PM, Artem Skvira <artem.skv...@gmail.com> wrote:

> Hi all,
>
> I have a strange problem.
>
> After successful oAuth session is established and request to, say,
> http://betastream.twitter.com/2b/site.json is sent, I start receiving
> some data.
>
> New tweets flow in, notification of deleted messages occasionally show
> up, the usual.
>
> However, after some time the activity ceases. If I look at the TCP
> connection in the list of OS connections - it is still there - or at
> least netstat tells me so:
>
> sudo netstat -p | grep
> node
>
> tcp        0      0 192-168-1-2.****.:34897 128.242.250.199:www
> ESTABLISHED 9008/node
>
>
> Do you have any idea why this might be happening? Could that possibly
> be twitter's fault? Can I somehow tell that connection became 'frozen'
> so I can re-start it?
>
> Thanks!
> Art
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk
>

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Reply via email to