There is a list of best practices on how to update your Filter Predicates in
the Streaming API doc:
http://dev.twitter.com/pages/streaming_api_concepts#updating-filter-predicates
Arnaud / @rno http://twitter.com/rno
On Fri, May 6, 2011 at 4:54 PM, Shannon Whitley
El 9/5/11 08:01, Arnaud Meunier:
There is a list of best practices on how to update your Filter Predicates in
the Streaming API doc:
http://dev.twitter.com/pages/streaming_api_concepts#updating-filter-predicates
Arnaud. Thanks for pointing us to these best practices.
I now have a question
Hey Faustino,
Yes, you can use an auxiliary connection (reducing your loss window using a
delta scheme, as explained in the doc) to manage query velocity. But that
really makes sense in a large predicates (higher access level) + frequent
updates context.
Arnaud / @rno http://twitter.com/rno
I'm working on a program that uses the stream api to listen for tweets
from a list of users, if that list of user changes it appears to me
that I need to drop connection and reconnect in order to listen to the
new list of users even if its just to add one new user. If I do this I
could loose
I need to attack this issue too, so I'm looking forward to suggestions.
On Fri, May 6, 2011 at 9:35 AM, Ray Slakinski ray.slakin...@gmail.comwrote:
I'm working on a program that uses the stream api to listen for tweets
from a list of users, if that list of user changes it appears to me
that I
