I'd strongly suggest consuming the Streaming API only from persistent
processes that write into some form of durable asynchronous queue (of any
type) for your application to consume. Running curl periodically is unlikely
to be a robust solution.
Select one of the existing Streaming API clients out there and wrap it in a
durable process. Write to rotated log files, a message queue, or whatever
other mechanism that you choose, to buffer the arrival of new statuses
before consumption by your application. This will allow you to restart your
application at will without data loss.
Services, Twitter Inc.
On Sat, Jan 16, 2010 at 10:27 AM, Jacopo Gio <jacopo...@gmail.com> wrote:
> Same for us, George.
> But what are the alternatives ?
> On Jan 15, 6:17 pm, GeorgeMedia <georgeme...@gmail.com> wrote:
> > I'm looking for a solid PHP library to access the gardenhose and just
> > wondering if anyone is successfully implementing this using phirehose.
> > It seems to be the only one out there...
> > This fairly dated code seems to work for random periods of time then
> > stops.
> > http://hasin.wordpress.com/2009/06/20/collecting-data-from-streaming-...