undefined | Better HN

0 pointsNegitivefrags12y ago0 comments

it's just a simple framing protocol over TCP

Websockets is ridiculous for this reason.

It has a stream abstraction (Websocket API) over a packet based protocol (Websocket Protocol) on top of streaming protocol (TCP) on top a packet protocol (IP).

This shit has to stop.

We had everything we needed. Websockets should have just been exposing regular sockets to the browser.

I don't buy the HTTP proxy argument.

0 comments

2 comments · 2 top-level

mbq12y ago

Except we have to deal with a lack of IPv4 addresses, DDoS attacks, load balancing, NATs, firewalls...

FooBarWidget12y ago

I used to think that. Until I realized that WebSockets added the following features that raw TCP doesn't have:

- Multiplexing multiple logical WebSocket servers on a single port, through the HTTP host header and URI.

- Authentication through HTTP basic or digest authentication.

Very, very useful features.

j / k navigate · click thread line to collapse