The websocket protocol has been touted as a great leap forward for bidirectional web applications like chat, promising a new era of simple comet applications. Unfortunately there is no such thing as a silver bullet and this blog will walk through a simple chat room to see where websocket does and does not help with comet applications. In a websocket world, there is even more need for frameworks like cometd.[Read More]
Posted at 04:27AM Mar 02, 2010 by gregw in General | Comments[6]
There is a jurisdictional issue brewing over the future of internet standards. The dispute is between the WHATWG and the IETF regarding the specification process for the websocket protocol.[Read More]
Posted at 11:01AM Jan 31, 2010 by gregw in General | Comments[18]
Jetty-7.0.1 has been extended with a WebSocket server implementation based on the same scalable asynchronous IO infrastructure of Jetty and integrated into the Jetty Servlet container.
[Read More]Posted at 03:46PM Nov 24, 2009 by gregw in General | Comments[19]
The W3C has developed the Websocket API proposal for HTML5, that enables web pages to perform two-way communication with a remote host. There is also a proposed IETF draft websocket protocol to transport the websocket messages.
I believe that there are significant deficiencies in the proposed websocket protocol and this blog looks at how they can be rectified.
[Read More]Posted at 02:32PM Oct 20, 2009 by gregw in General | Comments[8]
Bidirectional Web Transfer Protocol - BWTP
I really like the idea behind the HTML5 Websocket API - namely that a datagram model should be used for web application communication rather than a request/response paradigm (this is also the idea behind cometd). But unfortunately, the proposed protocol to carry websocket traffic is neither a good protocol nor is it well specified.[Read More]
Posted at 08:38PM Jul 01, 2009 by gregw in General | Comments[1]
