- From: Martin Thomson <martin.thomson@gmail.com>
- Date: Mon, 5 May 2014 09:50:42 -0700
- To: Erik Nygren <erik@nygren.org>
- Cc: Yoav Nir <ynir.ietf@gmail.com>, K.Morgan@iaea.org, "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>, C.Brunhuber@iaea.org
On 5 May 2014 08:50, Erik Nygren <erik@nygren.org> wrote: > I do think that the idea of a light-weight HTTP/2 profile may make sense. This has been proposed, but it wasn't considered interesting enough to specify. See [1]. I'm not sure if anyone has attempted to build an HTTP/2 implementation with some combination of minimal code size, processor usage, and memory footprint. As you point out here, it may be marginally more work than HTTP/1.1, and some features may be too tempting to pass up. HPACK with a table size of 0 is actually fairly simple to implement. Though I'm not sure that it's significantly easier to handle than HTTP/1.1, since the contents of the header fields are still textual(*). [1] tools.ietf.org/html/draft-montenegro-httpbis-http2-server-profiles
Received on Monday, 5 May 2014 16:51:10 UTC