Except we have to deal with a lack of IPv4 addresses, DDoS attacks, load balancing, NATs, firewalls...
Re:HTTP/2.0 – Please admit defeat
by FooBarWidget on Monday May 26, 2014 @04:59PM
(#7801611)
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.
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.