WebSocket is an API and a Protocol that have come from the Whatwg for the purposes of improving Comet support in the browser and on the network. The API is now being standardized by the W3C and the IETF is considering creating a WebSocket working group to standardize the protocol.
I’m not a big fan of the WebSocket protocol, as evidenced by my blog on how to improve WebSocket, the BWTP proposal and/or the IETF Hybi mailing list. But Chrome and Firefox will soon be supporting WebSocket, so WebSocket (for better or for worse) will soon be available in the wild.
So if you can’t beat them, join them. Having failed to convince others to create a better protocol, I’m now determined for Jetty to provide the best implementation of the protocol and to become the server of choice for WebSocket Comet development, deployment ( and experimenting with improving the protocol).
Jetty’s async IO architecture is ideally suited to providing a very scalable implementation of WebSocket that is well integrated with standard server-side java application environments. Thus Jetty-7.0.1 now includes a WebSocket server. Feedback welcome!