News for hackers. Stuff that matters.
Re:Last Call: HTTP2 by ddoolin on Thursday January 01, 2015 @08:11PM (#8825070)
Is there somewhere where you or someone else goes into more details on the points you made?
Re:Last Call: HTTP2 by jacquesm on Thursday January 01, 2015 @08:31PM (#8825120)
Re:Last Call: HTTP2 by youngtaff on Friday January 02, 2015 @06:14AM (#8826386)
PHK simultaneously complains that HTTP/2 doesn't go far enough e.g. replace cookies with a stateful mechanism, while also complaining the header compression and other mechanisms in HTTP/2 introduce the requirement for the server to maintain state.

PHK also refers to HTTP/2 as a political protocol and casts various aspertions about those promoting it but you need to remember that PHK isn't a neutral observer - Varnish does't support TLS yet (though PHK is very clear on why this is the case).

Re:Last Call: HTTP2 by Dylan16807 on Friday January 02, 2015 @08:14AM (#8826628)
>PHK simultaneously complains that HTTP/2 doesn't go far enough e.g. replace cookies with a stateful mechanism, while also complaining the header compression and other mechanisms in HTTP/2 introduce the requirement for the server to maintain state.

Sounds valid to me. Either retain state or don't.

Re:Last Call: HTTP2 by youngtaff on Friday January 02, 2015 @11:42AM (#8827393)
Maybe but changing the state semantics on the client is more work than just changing the protocol stack.

I suspect it will come in time but I'd argue it's better to develop incrementally rather than a big bang approach, and there's plenty in HTTP/2 to allow further improvement.