- From: Martin Thomson <martin.thomson@gmail.com>
- Date: Thu, 3 Nov 2016 11:06:50 +1100
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: Vlad Krasnov <vlad@cloudflare.com>, HTTP Working Group <ietf-http-wg@w3.org>
On 3 November 2016 at 05:26, Julian Reschke <julian.reschke@gmx.de> wrote: >> feed the dictionary into? HTTP/2 doesn't know about compression, in >> particular, HTTP/2 really *can't* use content-encoding. >> ... > > > What? HTTP/2 - at the layer Vlad is talking about - only knows about the bytes that comprise a request or response. What Vlad proposes requires that the HTTP/2 layer look at the Content-Encoding header field, determine that it *ends* with a compatible value and only then do things to feed data to the compressor. That's a massive architectural upheaval.
Received on Thursday, 3 November 2016 00:07:23 UTC