On: Enough with the JavaScript already

[jiggy2011]

I don't see the point of websockets, why not just let the browser make normal outbound TCP connections?

[dragonwriter → jiggy2011]

I think the main points WebSocket vs. unrestricted TCP sockets is:

1. Support for a browser-appropriate security model (origin-based)

2. Not requiring extra work to pass through HTTP-friendly (and everything-else-hostile) firewalls.

[jiggy2011 → dragonwriter]

I assume you would apply the same origin policy to the connections.

The firewall point is good, although I don't understand why you would want to block general TCP connections but not websock.

[FooBarWidget → jiggy2011]

A lot of corporate environments prevent you from connecting to anything but port 80 and 443. Websockets is the only way for you to multiplex your tcp-like connections over port 80.

[jiggy2011 → FooBarWidget]

Right, but I assume they block those other ports for a reason. What is different about websocket that makes that reason no longer apply?

[gsnedders → jiggy2011]

Because: we want a message-based protocol, and we want to make it (comparatively) hard to launch a DDOS attack using visitors to a website.