Re: hpack static table question?

• From: Cory Benfield <cory@lukasa.co.uk>
• Date: Mon, 2 Jun 2014 17:20:34 +0100
• To: Tatsuhiro Tsujikawa <tatsuhiro.t@gmail.com>
• Cc: Greg Wilkins <gregw@intalio.com>, Ilari Liusvaara <ilari.liusvaara@elisanet.fi>, HTTP Working Group <ietf-http-wg@w3.org>
• Message-ID: <CAH_hAJELU4vdHH3LivZSuJc9DvQ5A4G5XzBkP0Lhb5R_YAOr+w@mail.gmail.com>

On 2 June 2014 17:05, Tatsuhiro Tsujikawa <tatsuhiro.t@gmail.com> wrote:
> Sorry, I don't understand.  What is the problem here exactly?

Let's get everyone on the same page.

Greg is concerned that he has to copy a header out of the static table
into the header table in order to add it to the reference set. He has
to do this because the spec states that references may only be to
headers in the header set without being clear of _why_ that's the
case.

Tatsuhiro has provided the most compelling reason so far, which is
that it enables the clearing of the reference set by the slightly
obscure means of setting the header table size to zero via HTTP/2
SETTINGS. I don't think anyone actually wants to do this.

I think the real question here is: why can't we have references to the
static table? What is the architectural reason that ruled it out?

Received on Monday, 2 June 2014 16:21:02 UTC