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

Re: delta encoding and state management

From: Roberto Peon <grmocg@gmail.com>
Date: Thu, 17 Jan 2013 14:00:03 -0800
Message-ID: <CAP+FsNf1Mbf+VEc0H8g7viGFMKW4ze31_3wuRn8gWKJ2qGLiag@mail.gmail.com>
To: James M Snell <jasnell@gmail.com>
Cc: Nico Williams <nico@cryptonector.com>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
I don't believe you'll find an argument that finding a good or optimal
encoding is a bad thing.

So, lets do that part. We know about a few proposals for that already:
Delta, bohe, wap, etc.

I do disagree that good encoding is sufficient. Breaking things into
crumbs, for instance, still requires state at any entity that wishes to
understand the content. If you don't wish to understand the content, then
you obviously don't need to keep state.
Proxies and end-users often have competing motivations-- the end-user often
cares most about latency, the proxy about throughput. The idea here is
that, by allowing the decoder to control how much state the encoder uses,
at worst you collapse to just using the encodings. If that is slow and the
users/customers complain, then you increase the state size from zero so as
to decrease latency.

-=R

On Thu, Jan 17, 2013 at 1:44 PM, James M Snell <jasnell@gmail.com> wrote:

> nnot come up with optimized binary encodings for everything but we can get
> a good ways down the road optimizing the parts we do know about. We've
> already seen, for instance, that date headers can be optimized
> significantly; and the sepa
Received on Thursday, 17 January 2013 22:00:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 17 January 2013 22:00:32 GMT