The firehose solution should be very near realtime, and will work over HTTP.
On Mon, Nov 24, 2008 at 21:24, bham <[EMAIL PROTECTED]> wrote: > > Oh that'd be perfect for what I'm working on! > > I noticed a latency of about 10-15s between making an tweet and seeing > the same in Search API results. > > Would this firehose solution work any faster? Will it send > notifications over XMPP? Gnip is nice but the latency kills me. > > On Nov 19, 1:11 am, "Alex Payne" <[EMAIL PROTECTED]> wrote: >> Check out this blog post for a fairly recent survey of how to get data >> from Twitter:http://dev.twitter.com/2008/10/we-got-data.html >> >> Our "firehose" solution is in final load testing and should be >> entering testing with partners within days. >> >> On Tue, Nov 18, 2008 at 19:40, Xianhang Zhang <[EMAIL PROTECTED]> wrote: >> >> > I'm having a really hard time finding timely information about the >> > current state of a twitter push API. It seems extraordinarily >> > inefficient for me to be polling the server constantly to detect >> > updates and I would love to hear that there is a simpler, easy to use >> > alternative. Is there any information on how to build response driven >> > twitter application, preferably in Rails? >> >> -- >> Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x > -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
