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
[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
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,
