Yup. It is an advertorial. Kaazing like promoting their own "WebSocket Gateway", and they're in a great position to, owning websocket.org

By the way, at the moment I'm using Python's Twisted with a simple wrapper called txWS: https://github.com/MostAwesomeDude/txWS

I'm not a big fan of socket.IO, seems too complex for my needs. I was quite happy to discover txWS, it's literally one more function call and you can just write ordinary Twisted code with no changes, which is a relief.

Edit: I'm tempted to purchase websockets.co...

Update: I went and bought websocket.us and websockets.us, and put up my own small website about WebSockets. I just want to provide an alternative to Kaazing's site, that has no commercial focus.

As a link, http://websocket.us/

Shameless plug: SockJS is non-complex alternative to Socket.io, websockets polyfill.

Added to WebSocket.us, thanks!

While definitely having an agenda, I still found it a useful high-level guide.

True but some of the data looks to be "dated". According to Wikipedia, Safari, Chrome FF, and IE10 have WS support.

Man I hate these undated Internet articles. Publishers use it to sneakily squeeze out a few extra page views from stale content. Hate it when I fall for that.

Besides support in recent browsers, anything else inaccurate in it?

It is in the last paragraph. I thought the 90% of the article prior to that was a pretty good neutral overview of websockets vs prior 2-way alternatives.