Great, with Apple, Mozilla and now Google innovating in the browser sphere, it looks like browser will be evolving at a much more rapid pace.<p>Gah, let's hope Microsoft gets some vision for IE too. (or ditch it like Bing ditched Live)
I've implemented a Ruby version of WebSocket server (which is based on EventMachine and yet very experimental) - <a href="http://github.com/laktek/Web-Socket-Examples" rel="nofollow">http://github.com/laktek/Web-Socket-Examples</a>
The main challenge with bidirectional browser communication is really in the backend. It does not scale nearly as easy as easy as RESTful HTTP requests.<p>I'm sure Google has developed some serious technology to address this while building Wave. Wondering if some of it come to Google AppEngine anytime soon?
> The protocol is not raw TCP because it needs to provide the browser's "same-origin" security model. It's also not HTTP because web socket traffic differers from HTTP's request-response model.<p>If Websocket has something like crossdomain.xml does that mean we can build p2p applications on that?
google confuse me<p>how was this implemented before local storage? every current version of browsers supports it apart from chrome (and opera?)<p>saying that it is pretty awesome, web sockets have been a long time coming