That would be in the headers and prior to protocol breakout. I'm talking about a... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		api on Feb 13, 2017 \| parent \| context \| favorite \| on: Show HN: WebSocket-first development 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 on Feb 13, 2017 | [–]

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

lisivka on Feb 13, 2017 | [–]

Because of firewalls, proxies, and NAT.

api on Feb 13, 2017 | [–]

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

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact