W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2013

Re: HPACK encoder/decoder memory bounding

From: Martin Thomson <martin.thomson@gmail.com>
Date: Fri, 25 Oct 2013 10:46:46 -0700
Message-ID: <CABkgnnV_AigLL9n0ku2nkQyqLAoSL6Q9FTUuav8cO5P18+nmyw@mail.gmail.com>
To: Tatsuhiro Tsujikawa <tatsuhiro.t@gmail.com>
Cc: Fred Akalin <akalin@google.com>, Hervé Ruellan <ruellan.crf@gmail.com>, Osama Mazahir <OSAMAM@microsoft.com>, HTTP Working Group <ietf-http-wg@w3.org>
On 25 October 2013 10:37, Tatsuhiro Tsujikawa <tatsuhiro.t@gmail.com> wrote:
> This greatly simplifies the things.

It does not simplify things.  Primarily because settings become
negotiable, which is a significant complication.  Is this the only
setting that is negotiable?  How do we signal that settings are

At worst, the cost to an encoder of an increased header table size
setting is an inability to use the static header table.  That means,
worst case, the encoder has to send a few more literals on the wire.
This is not significantly worse than sending
SETTINGS_HEADER_TABLE_SIZE=0.  In some respects, it's actually better.
Received on Friday, 25 October 2013 17:47:13 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:19 UTC