undefined | Better HN

0 pointshackcasual9y ago0 comments

For one you need some concept of same origin/CORS. Don't want web sockets to provide an easy DoS vector

0 comments

api9y ago

That would be in the headers and prior to protocol breakout. I'm talking about after that. Why does web sockets have an extra layer of framing and other nonsense? Not to mention other "modes of operation." It's a socket. Give me a socket.

toomim9y ago

No kidding. It's just a new version of TCP, implemented on top of HTTP, which is implemented on top of TCP.

lisivka9y ago

Because of firewalls, proxies, and NAT.

api9y ago

You already have a TCP connection, so NAT and firewalls don't matter here. Proxies have to be web socket aware anyway.

j / k navigate · click thread line to collapse

0 comments

api9y ago

toomim9y ago

No kidding. It's just a new version of TCP, implemented on top of HTTP, which is implemented on top of TCP.

lisivka9y ago

Because of firewalls, proxies, and NAT.

api9y ago

You already have a TCP connection, so NAT and firewalls don't matter here. Proxies have to be web socket aware anyway.

j / k navigate · click thread line to collapse