Quoting Damon C <d.lifehac...@gmail.com>:

Just wanted to chime in that the documentation is, indeed, pretty
confusing. I'd suggest the description paragraph beginning with
something like:

"This parameter is only available to Firehose, Retweet, Link, Birddog
and Shadow clients."

I assume the recommended approach to not missing data on reconnects is
using two streams? Do any Ruby folk out there have suggestions on how
they're doing this? I'm currently using the voloko/twitter-stream gem.


I'm not exactly a "Ruby folk" but I have used the gem. Underneath, IIRC, is some fairly simple EventMachine logic. The gem itself is open source - I'd think the creator could build in Twitter's recommended / required consumption protocols easily, or an EventMachine hacker could do it.

Now that User Streams is in production, I'm planning to start up some Streaming testing again, and I was planning to use that gem. Maybe "we" should open tickets for feature requests? I'll ask for a User Streams endpoint and you can ask for the connection logic. ;-)

M. Edward (Ed) Borasky
http://borasky-research.net http://twitter.com/znmeb

"A mathematician is a device for turning coffee into theorems." - Paul Erdos

Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 

Reply via email to