@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.
