News for hackers. Stuff that matters.
Re:Strengthening HTTP: A Personal View by matthewmacleod on Wednesday August 06, 2014 @08:17AM (#8142059)
I'm not trying to shift the burden here, but the point made was along the lines of "HTTP2 is rubbish" - I've seen this a lot, with little to back it up.

But I'd say some of the benefits were:

- Server push support - Multiplexed requests/header compression/other performance improvements - Mandatory encryption support

Downsides are (from what I understand):

- Not a plaintext protocol

There may be more downsides, which I'm happy to hear about.

Re:Strengthening HTTP: A Personal View by jimktrains2 on Friday August 08, 2014 @02:39PM (#8154386)
> - Server push support

Couldn't a multi-part document already do this?

> - Mandatory encryption support

Couldn't they just have said "OK, HTTP 1.2 MUST be done over a TLS connection?" Also, didn't the TLS-always idea go away recently?

The downsides also include reïmplementing much of level 4 (congestion management, flow control, &c) and all of the complexity that goes with it.

Re:Strengthening HTTP: A Personal View by protonfish on Wednesday August 06, 2014 @09:06AM (#8142240)
Mandatory encryption support sounds like a good idea, but isn't that what the article was saying they aren't going to do? I would say the other things you mentioned are features, but not necessarily benefits. Server push is not something I want, and if I did, web sockets are probably a better solution. And those alleged performance improvements have yet to show a significant performance increase on real-world web sites.
Re:Strengthening HTTP: A Personal View by justincormack on Wednesday August 06, 2014 @08:28AM (#8142088)
Here is a thread about issues in serving it efficiently https://groups.google.com/forum/#!searchin/mechanical-sympat...