Re: HTTP/1.1 Multiplexing

2015-04-09 Thread Martin Thomson
On Thu, Apr 9, 2015 at 12:11 PM, Jason Duell wrote: > At this point the HTTP/2 ship has sailed. It's exceedingly unlikely that > we or any other browser vendor or the IETF are going to pivot to a modified > HTTP/1.1 to get the feature set here. Oh, I don't know... If someone can provide some so

Re: HTTP/1.1 Multiplexing

2015-04-09 Thread Jason Duell
At this point the HTTP/2 ship has sailed. It's exceedingly unlikely that we or any other browser vendor or the IETF are going to pivot to a modified HTTP/1.1 to get the feature set here. Sorry! Jason On Thu, Apr 9, 2015 at 11:53 AM, Daniel Stenberg wrote: > On Wed, 8 Apr 2015, max.bruc...@gma

Re: HTTP/1.1 Multiplexing

2015-04-09 Thread Daniel Stenberg
On Wed, 8 Apr 2015, max.bruc...@gmail.com wrote: A request begins by adding a header: X-Req-ID, set to a connection-unique value. The server responded with an exact copy of this ID, and a X-Req-Target header which specifies the location of the response(for server pushing mostly). The server se

HTTP/1.1 Multiplexing

2015-04-08 Thread max . bruce12
I wrote a very simple addition to HTTP/1.1 in which I plan to draft as a RFC soon, which allows multiplexing, prevents HOL blocking, and allows server pushing in HTTP/1.1. HPack could also be incorporated, via negotiation. The idea? A request begins by adding a header: X-Req-ID, set to a connecti