Comment on Show HN: WebSocket-first developmentparentComments−api9yThat 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.−toomim9yNo kidding. It's just a new version of TCP, implemented on top of HTTP, which is implemented on top of TCP.−lisivka9yBecause of firewalls, proxies, and NAT.−api9yYou already have a TCP connection, so NAT and firewalls don't matter here. Proxies have to be web socket aware anyway.
Comments
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.
No kidding. It's just a new version of TCP, implemented on top of HTTP, which is implemented on top of TCP.
Because of firewalls, proxies, and NAT.
You already have a TCP connection, so NAT and firewalls don't matter here. Proxies have to be web socket aware anyway.