websockets

Fortunately, WebSockets are specified to be able to connect over TLS, and proxying WebSockets to TCP was one of the first use cases for WebSockets.

However WebSockets is still premature: only Chrome supports it right now and even the server protocol isn't finalized yet.

Made Websockets working with reverse proxy(IIS) sitting in between the browser and a Golang app server.

You could wrap a UI around it in the browser, or use it server-side with any mainstream programming language that supports websockets.

I agree that WebSockets is definitely the way forward and that stuff like Comet are merely hacks.

Over the years I've employed it for many purposes, including client/server apps that today we might use Websockets to implement.

Any syncing via XHR or websockets can be the I and the O in I/O.

Our backend is built using the latest technologies, including Node.js, Redis, MongoDB, and WebSockets.

WebSockets have been capable of cross-origin communication since day one.

It was built before websockets were compatibly implemented across browsers.

Well, websockets introduced a massive new opportunity for advertisers to exfiltrate user data that wasn't even subject to the normal cross-site restrictions until recently in most browsers.

Comet is not dead because websockets is: 1.

At the same time though, support for WebSockets in major browsers is woefully little, with only Chrome currently supporting it in an active "release," and (I believe) support available in the Firefox trunk for a later version.

I love websockets, and have been waiting for them for a long time, however I am severely disappointed that there is no way to elevate permissions from the same origin "security" model, this is a huge limitation on the way towards purely client side javascript applications.

But nobody proposed eliminating Websockets, or requiring explicit user approval for connections.