The documentation should be pretty clear on this topic. One main connection, and perhaps an auxiliary connection to manage query velocity. You must not proliferate connections to work around rate limits. Instead, you must apply for higher access. Connections are expensive.
http://apiwiki.twitter.com/Streaming-API-Documentation#UpdatingFilterPredicates -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Wed, Feb 24, 2010 at 10:46 AM, Alam Sher <alamshe...@gmail.com> wrote: > Hi, > > What is the best practice if I have 20K twitter user base and I want > to track user's specific keywords via statuses/filter? > > Should I distribute the processing on multiple nodes, lets say open a > streaming connection tracking keywords for 5K users each (on different > IPs or same IP with different authenticating users)? > > Or just apply for a bigger access level and use a single connection to > get the whole thing. > > Thanks, > Alam Sher >
