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

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

From: <K.Morgan@iaea.org>
Date: Tue, 15 Jul 2014 09:37:05 +0000
To: <grmocg@gmail.com>, <Herve.Ruellan@crf.canon.fr>
CC: <kazu@iij.ad.jp>, <ietf-http-wg@w3.org>, <tatsuhiro.t@gmail.com>, <martin.thomson@gmail.com>, <gregw@intalio.com>
Message-ID: <0356EBBE092D394F9291DA01E8D28EC201187F243B@SEM002PD.sg.iaea.org>
Hi Roberto-

On Tuesday,15 July 2014 07:34, grmocg@gmail.com wrote:
> ... or have opcodes which modify ranges of entries, ...

Did you also look at "having opcodes which *reference* ranges of entries"?

A week or so ago Herve mentioned this as an alternative to the reference set.  During my research of header compression I came to the same idea and found it to improve the compression factor much in the same way as a reference set.

As you have mentioned before, and I concur, applications will eventually adapt to the compression mechanism.  I believe this would also be true for referencing ranges of entries from a header table. While it couldn't achieve the same compression as a reference set, it could come really close as applications start shaping the header set to contain the largest possible contiguous range of headers which are repeated from request to request.

-keith



This email message is intended only for the use of the named recipient. Information contained in this email message and its attachments may be privileged, confidential and protected from disclosure. If you are not the intended recipient, please do not read, copy, use or disclose this communication to others. Also please notify the sender by replying to this message and then delete it from your system.
Received on Tuesday, 15 July 2014 09:37:47 UTC

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