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

Re: Recovery from decompression failure (was: Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues))

From: Poul-Henning Kamp <phk@phk.freebsd.dk>
Date: Thu, 24 Jul 2014 14:35:01 +0000
To: Martin Thomson <martin.thomson@gmail.com>
cc: Tatsuhiro Tsujikawa <tatsuhiro.t@gmail.com>, Mark Nottingham <mnot@mnot.net>, David Krauss <potswa@gmail.com>, Greg Wilkins <gregw@intalio.com>, HTTP Working Group <ietf-http-wg@w3.org>, Michael Sweet <msweet@apple.com>, Jason Greene <jason.greene@redhat.com>, Roberto Peon <grmocg@gmail.com>, Ilari Liusvaara <ilari.liusvaara@elisanet.fi>
Message-ID: <59546.1406212501@critter.freebsd.dk>
In message <CABkgnnV82KWYVzHKNzFH7fXp4hZoC7vsqGsJcPDRep-O1qKuQQ@mail.gmail.com>
, Martin Thomson writes:

>Yes, I would use SETTINGS ACK as the marker to use for trimming the
>header table down, but still require the next header block after that
>to include a context update.  That might mean two rounds of eviction
>if the encoder chooses to use a smaller table size, but that's the
>safest approach.

The safest and by far most efficient approach is to have an oopcode
for it.

Why that was felt necessary for the reference set but not for the
dynamic set is a good question.

Resizing the dynamic set to zero and then back up invites the
receivers to complicate their memory management because the most
likely resize of the dynamic set isn't going to be one.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.
Received on Thursday, 24 July 2014 14:35:30 UTC

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