Hacker News new | ask | show | jobs
by api 3412 days 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.
2 comments
toomim 3412 days ago
No kidding. It's just a new version of TCP, implemented on top of HTTP, which is implemented on top of TCP.
link
lisivka 3412 days ago
Because of firewalls, proxies, and NAT.
link
api 3412 days ago
You already have a TCP connection, so NAT and firewalls don't matter here. Proxies have to be web socket aware anyway.
link