Re: [twitter-dev] Question about User Vs Site Streams, and Moving away from REST calls.

2010-09-16 Thread John Kalucki
I'm sorry, I laid out the difference between User Streams and Site Streams, but I forgot to bring it all back to the specific question at hand. The critical difference isn't Desktop vs. Web Site-- that's the general case description. The key difference is that you must multiplex if you open more t

Re: [twitter-dev] Question about User Vs Site Streams, and Moving away from REST calls.

2010-09-15 Thread Tom van der Woerdt
Hi John, This seems like a rather strange policy. Is the cost of having one User Streams connection not far lower than having a connection to Site Streams? That's what Justin asked, just one connection. Tom On 9/16/10 6:22 AM, John Kalucki wrote: > Our intention is that User Streams and Site St

Re: [twitter-dev] Question about User Vs Site Streams, and Moving away from REST calls.

2010-09-15 Thread John Kalucki
Our intention is that User Streams and Site Streams will, shortly, offer the same data and filtering options at a similar, if not identical, QoS. I'm sure some subtleties will creep in over time, as they always do, but this parity is our goal. The major difference is that User Streams, given its h

[twitter-dev] Question about User Vs Site Streams, and Moving away from REST calls.

2010-09-15 Thread Justin
I've successfully migrated one of my sites away from making search and mention rest calls, switched over to the streaming API and I'm loving it. I still need to move it to OAuth but now that I have that in test I'm reading up on the User and Site streams and I have a question. It seems the User st