W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2014

Re: hpack static table question?

From: Greg Wilkins <gregw@intalio.com>
Date: Mon, 2 Jun 2014 17:17:46 +0200
Message-ID: <CAH_y2NFiZZ12qZ0BdTBCiUwMbEkpKMMd2KN18pfQN-0BqoHu4w@mail.gmail.com>
To: Ilari Liusvaara <ilari.liusvaara@elisanet.fi>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Hmmmm, Currently there is no state I can see for the header table entries?
They are either in the table or not and the only eviction mechanism is due
to size.    There is no need to keep set/emitted bits, as that is for the
reference set and not the header table.

So I'm still missing something?



On 2 June 2014 17:07, Ilari Liusvaara <ilari.liusvaara@elisanet.fi> wrote:

> On Mon, Jun 02, 2014 at 04:45:28PM +0200, Greg Wilkins wrote:
> > The hpack draft 7 says in 3.2.1 : "The referenced static entry is
> inserted
> > at the beginning of the header table".
> >
> > I can't understand why this copy of a static entry to the dynamic table
> is
> > needed?   Doesn't this mean that the static entry will now be known by
> two
> > indexes?     Why is this copy needed?
>
> AFAIK, to avoid needing having to keep state bits (2 per entry[1]) for the
> static table.
>
> Yeah, the static table is 61 entries, thus the amount of state needed would
> be just 16 bytes.
>
>
> [1] In set and emitted bits.
>
>
> -Ilari
>



-- 
Greg Wilkins <gregw@intalio.com>
http://eclipse.org/jetty HTTP, SPDY, Websocket server and client that scales
http://www.webtide.com  advice and support for jetty and cometd.
Received on Monday, 2 June 2014 15:18:16 UTC

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