When my program makes hundreds of connections with Site Stream to
observe tens of thousands of users, the latency for every status
messages seems to start off like 10~30 minutes. It gradually gets
better and will be like 0~1 seconds within an hour or two, though.

Is this expected behavior?

Because this wouldn't be the case when it'd make much much fewer
connections, I'm guessing something must be wrong somewhere. The
traffic isn't any issue and my program can handle much more data

It appears to me that Site Stream server is taking too much time to
send out many "friend list" to clients.

Any thoughts?

Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 

Reply via email to