Thanks John! One last question: how can I contact Twitter if I need a API stream agreement as we start to have more users. Is that an email to where I should write about increase the limit of the stream API?
Thanks--Joao On May 27, 5:04 am, John Kalucki <[email protected]> wrote: > The best way to find out is to jump in and start experimenting! curl > (1) works great to get started. > > The output from the exposed Streaming API methods is identical. A > stream of tweets, optionally delimited by length. As new statuses are > posted that match your query's selectivity, they are written > immediately on the TCP socket. You read them with a HTTP client that > is capable of incremental reads. After that, you are on your own, > route them within your application as you see fit. > > -John Kalucki > Services, Twitter Inc. > > On May 26, 11:42 am, techtimes <[email protected]> wrote: > > > Hi, > > > If I follow 150 users via the streaming api Url > > http://stream.twitter.com/follow.format > > > Hows does it works in practice: > > > 1: is data pushed to the URL? > > > 2: does the URL can ping my application when new updates are ready to > > be collected? > > > Thanks > > Joao
