Thanks Nic, WebSockets are not production ready.
Here is the latest spec: http://tools.ietf.org/html/draft-hixie-thewebsocketprotocol-74 I was basing the talk off of revision ~55. For the most part, what we explained about WebSockets, holds true. --Dan On Fri, Mar 5, 2010 at 10:30 AM, Nic Benders <[email protected]> wrote: > First off, thanks to Dan Simpson and Nick Zadrozny for the cool intro talk > on the emerging WebSocket technology. > > For those interested in following what is still a moving target here is the > IETF draft of the protocol, and the W3C draft of the JS API. > > http://www.whatwg.org/specs/web-socket-protocol/ > > http://dev.w3.org/html5/websockets/ > > Both of these documents have been updated in the last day (!). Notable > changes include a new, rather complex, initial handshake > using Sec-WebSocket-Key fields in order to provide some security against > just packing XHR or POST to a WebSocket server. > > Since Chrome is the only shipping browser with WebSocket support, I doubt > that people were rushing out to put this stuff into production yet, but this > is just a reminder that the spec is very much still in flux. I wouldn't be > surprised if this handshake issue sees several more major revisions in the > next few months. > > -- > SD Ruby mailing list > [email protected] > http://groups.google.com/group/sdruby -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby
