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

Re: delta encoding and state management

From: Nico Williams <nico@cryptonector.com>
Date: Thu, 17 Jan 2013 12:46:54 -0600
Message-ID: <CAK3OfOhQvwiDNGxAg1ARnrORorSQ+4m-thk16OL9eytgb1vmkA@mail.gmail.com>
To: James M Snell <jasnell@gmail.com>
Cc: Roberto Peon <grmocg@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>
On Jan 17, 2013 11:57 AM, "James M Snell" <jasnell@gmail.com> wrote:
>> If the compression is hop-by-hop then there's no synchronization
>> issues.  But then middleboxes may have to decompress and always
>> re-compress (even if the headers are left unmodified) in each
>> direction.
>>
>
> That's the exact problem I'm having really. Middleboxes will be required
to maintain a complete compression state (for requests and responses) as
opposed to just passing things through. Maintaining that state could become
quite expensive. If we don't maintain it, tho, the potential sync issues
become too messy.

Right, if you want to do dreadful compression then middleboxes will have to
be stateful.

>>
>> In general I'd much rather not have connection-oriented state at all,
>> not even if it were transparent to HTTP.
>>
>
> Agreed, not sure how to avoid it and still get good compression (outside
of simply optimizing the encoding of values as much as possible... i.e.
bohe)

I'd rather do the architecturally-clean thing: optimize encodings.

Nico
--
Received on Thursday, 17 January 2013 18:47:21 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 17 January 2013 18:47:26 GMT