At Review19 - <a href="http://review19.com" rel="nofollow">http://review19.com</a> - we are primarily using web sockets but we have fallback / failover transports in place.<p>What helps is the very awesome Socket.io abstraction, just mention websockets and a bunch of fallbacks in the config and get coding.<p>Must say having JavaScript on the server, the client and the data store is a huge advantage as well from a programming context perspective!
"Stable and ready for developers" and mixing it with links to the .Net framework 4.5 beta documentation seems off.<p>Sure, it can be stable. And ready is kind of subjective. But the 'Use this, now' feeling I got from the title was quickly nowhere to be found.<p>That said: I liked the whole walkthrough and general depth of the article.
Huh? Android default browser (and most importantly, WebView) does not support WebSockets, and has no visible plans to support it. IE8/9 do not support WebSockets.
One of the very <i>real</i> issues with WebSockets is that they don't work often over mobile networks, with invisible proxying, etc.<p>Unless you go with something like Socket.IO, WebSockets alone would never be a viable solution.
Websockets are great, but apache and nginx are still yet to support them out of the box. You have to recompile nginx with a module and apache has to have a custom mod.<p>When it's a case of writing in a line in nginx.conf for a proxy bypass or commenting out an apache module then it will be ready. Using port HTTP/port 80 is one of websockets strengths.
Does anybody know how fast connecting to a WebSockets server is? How does it compare to connecting over http? I was interested in the ws:// uri scheme as I was unaware of that. Is there a future scenario where we could connect to a WebSockets server directly through the browser without first connecting over http and then with js?
By a guy from Microsoft so plenty of MS examples/links, but a good overview of WebSockets never the less. I'm interested to hear how many of use will ever actually use the `WebSocket` object? Will we (developers) always use a library offering a layer of abstraction and the real core functionality that we need.
On a related note we put out a tech demo showing nodejs and socketio recently. <a href="http://www.webdigi.co.uk/fun/space/" rel="nofollow">http://www.webdigi.co.uk/fun/space/</a>
It uses iPhone accelerometer to control the ship on your browser game!
Microsoft technology examples. I am a-feared. Are there wrappers in jQuery or Prototype (et al) for browser side WebSockets access yet, so I only need to worry about <i>if</i> it is supported, rather than how?<p>Similarly, what does it take to support this on the server side? (in a *nix environment)