ah ok that is neat. eta?
On Nov 27, 12:34 pm, "Alex Payne" <[EMAIL PROTECTED]> wrote: > It's HTTP-push. You open a socket, we push data to you. The > transport just happens to be HTTP. > > > > On Wed, Nov 26, 2008 at 23:18, bham <[EMAIL PROTECTED]> wrote: > > > @fastest963: Well I was thinking of using Twitter for some nice simple > > automated communication and for my application 10-15s is a little > > slow. > > > @Alex: What do you mean works over HTTP? So I'd have to poll? How is > > that a firehose solution? I'm genuinely confused. > > > On Nov 26, 11:02 pm, fastest963 <[EMAIL PROTECTED]> wrote: > >> As far as I know, the Firehose API would only be for retrieving data > >> from Twitter and not sending (POST). > > >> @bham 10-15s isn't that bad? If it was over a minute then I would be > >> concerned. As far as the latency, I can assume that it is just because > >> of the caching that Twitter has put into place. > > -- > Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
