2 ms·
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 nonsens
by api 10y 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.
- toomim 10y agoNo kidding. It's just a new version of TCP, implemented on top of HTTP, which is implemented on top of TCP.
- lisivka 10y agoBecause of firewalls, proxies, and NAT.
- api 10y agoYou already have a TCP connection, so NAT and firewalls don't matter here. Proxies have to be web socket aware anyway.