I've got my "tweetstream" test started - filter keyword is "haiti" -
it's delivering tweets about 2 - 5 per minute at the moment.

On Feb 20, 10:16 pm, John Kalucki <j...@twitter.com> wrote:
> I have a hunch that this doesn't happen on sample, or, if it does so, it
> happens much more rarely.
>
> On Sat, Feb 20, 2010 at 9:26 PM, M. Edward (Ed) Borasky 
> <zzn...@gmail.com>wrote:
>
> > I've got the "tweetstream" Ruby gem installed and I have a test driver
> > program. I can fire this up if it will give anything useful. Is this
> > happening just on "filter" or would it happen on "sample" too?
>
> > On Feb 20, 9:02 pm, John Kalucki <j...@twitter.com> wrote:
> > > Arg. This is what I get for not checking the configuration each time.
> > Yes,
> > > it's currently set to send a newline every 30 seconds.
>
> > > On Sat, Feb 20, 2010 at 8:45 PM, Marc Mims <marc.m...@gmail.com> wrote:
> > > > * John Kalucki <j...@twitter.com> [100220 20:24]:
> > > > > A 45 second period of inactivity is not unusual when following just
> > 100,
> > > > or
> > > > > even 100,000 users. The keep-alive newlines are only sent once every
> > 10
> > > > > minutes. You should not reconnect so aggressively.
>
> > > > I can certainly set the time out to 10 minutes.  I'm seeing newlines in
> > > > the stream every 30 seconds, except for rare occasions. I understood
> > > > those to be keep-alive packets.  Apparently they are not and should not
> > > > be relied on?
>
> > > > @semifor

Reply via email to