From what I understand of Websockets, its bascially used to set up a two-way socket connection and not really an application protocol. What worries me the most is that you’ve basically rolled back 20 years of protocol consolidation, and we’re now back to a free-for-all of everybody’s pet protocol. Not so bad if your client and server are a tightly coupled, unreusable UI application. Really bad if you’re writing a web service that is supposed to be reusable by unknown heterogenous clients. With Web Sockets, web services are not only going to have to negotiate the media type, but also the application protocol. Seems like a huge step backward to me in terms of integration. Did we forget all the problems we had with Oracle Forms, PowerBuilder, Visual Basic and all the UI/framework specific protocols all those developer frameworks introduced? Do we really want to go back to those days?
What about security issues? With an anything-goes socket protocol, isn’t this a security nightmare for our operations folks?
Disclaimer: You could say that I’m both biased and threated by the concept of Web Sockets given my involvement in REST frameworks and APIs. But in all honesty, I’d be very happy to embrace a new protocol that is both ubiquitous and easily supportable and interoperable in many different languages and platforms. There’s much to be said about the simple request/response text-based approach of HTTP (and REST over HTTP). While it may not be uber-efficient, its just so easy to hack and support.