The first release of User Streams is not intended for web clients due to capacity constraints.
http://apiwiki.twitter.com/ChirpUserStreams " All services, mobile and browser-based clients must not use Streaming until we've sorted out Desktop clients at some scale. One problem at a time. " That being said, of course we'd like to encourage experimentation with other client types, so that clients can evolve as we scale out the service. While others at Twitter are well-versed in the latest browser technologies, I'm totally and willfully ignorant. If you could give a brief summary of how the existing Streaming API does not work for WebSockets, that might be helpful. What's missing? -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Fri, May 14, 2010 at 9:38 PM, Cezar Sá Espinola <[email protected]> wrote: > Hey guys, > Quick question, are there any plans on supporting WebSockets protocol for > the Streaming API? > That'd be awesome for browser based Twitter clients (i.e. Google Chrome > extensions). Without this it'll be very difficult for this kind of client to > lavarage benefit from the upcoming user streams. > Thanks a lot for all your hard work, > Cezar Sá Espinola > @cezarsa
