Re: [twitter-dev] Streaming Site API hogs at some stage
The approach that Tim mentions is a good backstop, but this covers for an operational situation at Twitter that almost never happens. If you are seeing this condition happen often, there's probably something else wrong somewhere. If it is on our end, I'd like to fix it, but chances are its on your end, as there are no other reports of this situation. Do you have NAT or a HTTP proxy, either in hardware or software, between your server and the internet? If so, it may be dropping sessions, leaving your session high and dry. -John On Sun, Jan 2, 2011 at 6:56 AM, Tim Haines tmhai...@gmail.com wrote: 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.comwrote: 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 tcp0 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 -- 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-dev] Streaming Site API hogs at some stage
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 tcp0 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
Re: [twitter-dev] Streaming Site API hogs at some stage
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 tcp0 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
