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

Re: Consequences of removing the reference set

From: Roberto Peon <grmocg@gmail.com>
Date: Thu, 24 Jul 2014 11:30:28 -0700
Message-ID: <CAP+FsNemNZkLjoRUACXD6Na7-pW1mNKXwYiWjv8uqewx+_fbWQ@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
I'd suggest keeping it unless we have data suggesting it isn't necessary.
It isn't exactly the most complex of things.
-=R


On Thu, Jul 24, 2014 at 11:26 AM, Martin Thomson <martin.thomson@gmail.com>
wrote:

> On 24 July 2014 11:03, Roberto Peon <grmocg@gmail.com> wrote:
> > I believe that it would make sense to potentially (at the compressor's
> > option) have same-named header fields referenced by a single op-code.
> > Analysis may prove that this is a needless concern though.
>
> What do you suggest that we do?  Based on the information we have on
> the two options, the reduced complexity suggests that '\0'-concat
> isn't worth it.  Unless you would like to find some more information
> to tilt the scales in the other direction.  I'd suggest that would
> need to happen quickly, just as I suggested the same to Herve when he
> suggested we use ranges for header table references (though that would
> require tuning in addition to tests).
>
Received on Thursday, 24 July 2014 18:30:54 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 30 March 2016 09:57:09 UTC