W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2013

Re: All changes but huffman encoding integrated + a question

From: Roberto Peon <grmocg@gmail.com>
Date: Tue, 15 Oct 2013 21:07:07 -0700
Message-ID: <CAP+FsNfy3jyE+dfsnvPLbo=SSrDMU7brapXThZDpHdd0g=fa7A@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
The problem here occurs when one is evicting what one is adding.

This can be handled without ever using more memory that allocated to the
compression context. One can also deal with this by copying just the name
(as opposed to the whole name+value-list), if one is willing to trade size
for complexity.

A ring buffer *is* a linear memory model-- it requires only a linear range
of memory. When I talk about a linear memory model without heap
fragmentation, this is what I am talking about.

On Oct 15, 2013 8:35 PM, "Martin Thomson" <martin.thomson@gmail.com> wrote:

> On 15 October 2013 19:25, Roberto Peon <grmocg@gmail.com> wrote:
> > 2) Make this illegal; This makes the encoder more complex as the encoder
> > must attempt to do this encoding and then check to see if actually fit
> every
> > time it does this kind of header representation.
> Not to want to contradict Tatsuhiro, but I thought that you argued
> pretty strongly for this one.  Something about a linear memory model.
> I got the impression that this was OK with people, mainly because it
> was perfectly consistent: evict, then add.
> Did something change?
Received on Wednesday, 16 October 2013 04:07:34 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:43:38 UTC