I was trying to understand the Streaming API(T4J..SiteStreamListener)
data-flow and have got few questions:

How does the data-flow happens, is there are temporary storage
mechanism in the T4J API itself when underlying client consumer is
busy with the current tweet AND the stream is about to push hundreds
of thousands of matching/filtered tweets


Is the incoming data paused @ Twitter end for waiting to the
connection to be ready to accept the data, but since that is push
based model the Twitter end would throw the data to the client
irrespective of its acceptance state.

Also I am thinking about instantiating # of stream listeners in my app
for certain type of queries, does Twitter impose any limit of max# of
queries through a client-app OR does your API impose that limit?

I have been reading that there's practically no limit for data-flow
for the streaming API.

I am trying to gauge whether I <b>really</b> need a app-local
buffering mechanism for the huge # of incoming tweets for not blocking
the incoming stream and doing my consumption in a normal
fashion(without local buffering) OR does it naturally works with
Twitter + T4J?



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