h5bp/html5please — pull request #77 by leggetter (2012-01-24 11:34:42+00:00)
Title: Encourage use with technologies other than Node.js and socket.io

The main reason for this commit is that I'm very keen to help developers who don't want to use Node.js, or have a different technology preference, use WebSockets and I think encouraging them to use other back-end technologies (.NET, Ruby, Python) where there are WebSocket server solutions will encourage the uptake of this technology even more.

Details:

* web-socket-js is the most commonly used polyfill so I've updated to mention this first so that the priority is to help developers be able to use the `WebSocket` object within the web page.
* Removed socket.io as a polyfill. It's not a polyfill, it offers a framework that handles connection fallback for you. When using socket.io developers don't then directly use a `WebSocket` object as you do with a polyfill; you use the socket.io client library objects.
* Removed the term 'Comet'. 'tune your Comet' didn't really make sense and Comet is a paradigm, an umbrella term, and Comet servers quite frequently use WebSockets so it's incorrect to say Comet and WebSockets are two different things.
* Added XSockets as a framework with fallback support on a par with socket.io. It doesn't have fallback support beyond Flash and Silverlight so maybe that's a reason not to include it?

I'm maintaining a list of servers with WebSocket support [here](http://www.leggetter.co.uk/real-time-web-technologies-guide#self-hosted) but didn't want to self promote.