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 <dan...@haxx.se> wrote: > 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 sets the X-Req-ID = push/based-id for pushed >> responses. In doing so, we do away with the standard in-order processing & >> one-response-per-request model. >> > > In "doing away" with that, you're also no longer HTTP/1.1 compliant (which > is a pretty significant drawback) and you also miss a few of the definite > benefits that HTTP/2 brings: like priorities and HPACK on the first request. > > My guess is that you will have a hard time to convince HTTP people that > this is a good idea worthy to implement even when you call it something > else than 1.1. But then that's just my opinion. > > -- > > / daniel.haxx.se > > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > -- Jason _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
