Thought I'd chime in here and add my support for Phrirehose - Fenn,
nice work!
We just did our first test-run with Phirehose on Sunday to track all
of the traffic related to Super Bowl ads. At peak, it was pulling a
consistent 120 tweets/sec with ease. We were only limited by our
account's
Hey Guys,
I'm the author of Phirehose so thought I'd jump in with some quick
thoughts -
Russ, you're spot on - what you describe there is exactly how
Phirehose is designed to be used.
For both of your guys use cases, the number of tweets seems to be very
low (ie: ~200/week), in which case, to
I too am using Phirehose for a similar small no. of tweets.
The general idea with streaming is not to process stuff live on the
wire but to parse it into files or a DB and then further process this
data from some additional code.
As an example: I am looking to get geocoded tweets for specific
