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
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 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
