News for hackers. Stuff that matters.
Re:HTTP/2.0 – Please admit defeat by icebraining on Monday May 26, 2014 @06:09AM (#7799233)
The future of network programming seems like it will be "TCP --> HTTP -(upgraded connection)-> WebSockets --> actual application layer protocol".

It's not like WebSockets runs "over" HTTP, it just uses an HTTP-like handshake; besides that, it's just a simple framing protocol over TCP.

That's why you can use a simple proxy to "websocket-ify" applications that use plain-old raw TCP connections.

Re:HTTP/2.0 – Please admit defeat by Negitivefrags on Monday May 26, 2014 @07:03AM (#7799305)
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.

Re:HTTP/2.0 – Please admit defeat by mbq on Monday May 26, 2014 @08:51AM (#7799527)
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.

Re:HTTP/2.0 – Please admit defeat by jballanc on Monday May 26, 2014 @06:30AM (#7799259)
Right, that's why I said we're adding one layer (not two).

Still, if TCP is the transport layer, and HTTP/SMTP/etc. are the application layer, then what do we call WebSockets when we implement an application layer protocol on top of it? The application compatibility layer?

In the past we had operating systems with network stacks and shared libraries for working with application protocols. Now we have browsers with network stacks and JavaScript libraries for working with application protocols. Wasn't it just a few days ago that someone was proposing an OS that would do just enough to boot a browser, and then let the browser handle most of the "traditional" operating system tasks? How long before we see a proposal for "lowering" WebSocket connections to the TCP layer?

This is what I mean when I say that we risk finding ourselves 20 years in the past. HTTP isn't ubiquitous because it is better. It's better because it is ubiquitous. If we don't pay attention to why things like WebSockets are easier to use today than raw TCP, then history will repeat itself.

Re:HTTP/2.0 – Please admit defeat by mattgreenrocks on Monday May 26, 2014 @11:50AM (#7800217)
Preach it.

I haven't seen anything that actually requires a new OSI layer, only people trying to reinvent lower-level layers poorly to address gross incompetence.

The Internet is more than the Web, and the Web will eventually be replaced.

Re:HTTP/2.0 – Please admit defeat by M2Ys4U on Monday May 26, 2014 @07:24AM (#7799342)
>Wasn't it just a few days ago that someone was proposing an OS that would do just enough to boot a browser, and then let the browser handle most of the "traditional" operating system tasks?

We already have that - Firefox OS: https://www.mozilla.org/en-US/firefox/os/