It turns out it was an issue with yajl-ruby, the current gem has a bug
which causes random disconnects, head in git does not however. Thanks
for helping me track down the problem!

Ben

On Aug 12, 11:11 pm, John Kalucki <j...@twitter.com> wrote:
> I can see from the logs that, on at least one occasion, your account was
> logging in too often and was login rate limited. Log in once and keep the
> connection open as long as possible. If you keep churning the connection,
> you'll get limited, and eventually banned.
>
> -John Kaluckihttp://twitter.com/jkalucki
> Twitter Inc.
>
>
>
> On Thu, Aug 12, 2010 at 12:26 PM, benofsky <b...@benmcredmond.com> wrote:
> > Hi,
>
> > I'm getting a lot of 401 errors on the streaming api using the sample
> > method. I am using basic authentication through the username
> > clarity_li. I am backing off as suggested in the documentation, with
> > an initial wait of 10 seconds, doubling each 4xx error and capping at
> > 240 seconds.
>
> > I can't work out why this is happening, it usually works for a few
> > minute before this happens, if I get disconnected intentionally I wait
> > 1 second before reconnecting, if there is a network error I follow the
> > guidelines in the documentation.
>
> > The only other reason supplied in the docs which could be causing this
> > is if the client is too slow, but I am on a 100mbps university
> > internet connection and take approximately 1ms to process each
> > incoming tweet.
>
> > I would be very grateful for any help.
>
> > Regards,
> > Ben

Reply via email to