Re: Call for Consensus: Remove "reference set" from HPACK (to address #552)

On 16 July 2014 16:08, Willy Tarreau <w@1wt.eu> wrote:

> I mean, the current design allows you to have a header field whose value
> changes between consecutive requests (eg: a proxy aggregating multiple
> users' requests), and still have that changing value referenced with
> little overhead.
>

That is still possible.

If one user sends a field

   wibble: now is the time for all good men to come to the aid of the party

that will be sent literal name and value and will go into the header
table.  Then when another user sends

  wibble: the moon is blue to a fish in love

That can be sent as a literal, but with indexed name - pointing to the
previous entry (but the value is ignored).

Now both fields are in the table and both can be used with a single index
reference.  If they are in the first 64, then it is only a single byte.

cheers








-- 
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.