Re: HTTP router point-of-view concerns

Martin Thomson <martin.thomson@gmail.com> Thu, 11 July 2013 16:37 UTC

Resent-Date: Thu, 11 Jul 2013 16:36:37 +0000
Resent-Message-Id: <E1UxJrB-0002Nn-7f@frink.w3.org>
MIME-Version: 1.0
In-Reply-To: <51DE327C.7010901@treenet.co.nz>
References: <CA+qvzFPUpcm6kUtJx+rTw8Dpp4Gtx4Bmr3XPDhjNsjchUfN9_w@mail.gmail.com> <51DE1E32.9010801@treenet.co.nz> <CAP+FsNdcYhA=V5Z+zbt70b5e7WmcmXgjG5M9L3vfXeXfTwmRnw@mail.gmail.com> <51DE327C.7010901@treenet.co.nz>
Date: Thu, 11 Jul 2013 09:36:02 -0700
Message-ID: <CABkgnnXeqD6wh0dcJ1Dz=4PLAJNkDeGcCuzMr9ATd_7xS7nbGQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Amos Jeffries <squid3@treenet.co.nz>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: text/plain; charset="UTF-8"
Received-SPF: pass client-ip=209.85.212.169; envelope-from=martin.thomson@gmail.com; helo=mail-wi0-f169.google.com
Subject: Re: HTTP router point-of-view concerns
Archived-At: <http://www.w3.org/mid/CABkgnnXeqD6wh0dcJ1Dz=4PLAJNkDeGcCuzMr9ATd_7xS7nbGQ@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list

On 10 July 2013 21:20, Amos Jeffries <squid3@treenet.co.nz> wrote:
> It seems not to be negotiable from the recipients side.

Compression context size = 0 is entirely negotiable from the recipient
end, with a small wrinkle, that I know some folks are working on.
Which is, a client can start using a default compression context size
prior to learning that a server has no space (substitute intermediary
as appropriate there).

HTTP router point-of-view concerns Christian Parpart
Re: HTTP router point-of-view concerns Amos Jeffries
Re: HTTP router point-of-view concerns Roberto Peon
Re: HTTP router point-of-view concerns Amos Jeffries
Re: HTTP router point-of-view concerns Christian Parpart
Re: HTTP router point-of-view concerns Amos Jeffries
Re: HTTP router point-of-view concerns Michael Sweet
Re: HTTP router point-of-view concerns Martin Thomson
Re: HTTP router point-of-view concerns James M Snell
Re: HTTP router point-of-view concerns Sam Pullara
Re: HTTP router point-of-view concerns Roberto Peon
Re: HTTP router point-of-view concerns Roberto Peon
Re: HTTP router point-of-view concerns Amos Jeffries
Re: HTTP router point-of-view concerns Sam Pullara
Re: HTTP router point-of-view concerns Patrick McManus
Re: HTTP router point-of-view concerns Roberto Peon
Re: HTTP router point-of-view concerns James M Snell
Re: HTTP router point-of-view concerns Roberto Peon
Re: HTTP router point-of-view concerns James M Snell
Re: HTTP router point-of-view concerns Roberto Peon
Re: HTTP router point-of-view concerns Sam Pullara
Re: HTTP router point-of-view concerns Roberto Peon
Re: HTTP router point-of-view concerns Martin Thomson
Re: HTTP router point-of-view concerns Poul-Henning Kamp
Re: HTTP router point-of-view concerns Mark Nottingham
Re: HTTP router point-of-view concerns Mike Belshe
Re: HTTP router point-of-view concerns Gábor Molnár
Re: HTTP router point-of-view concerns Gábor Molnár
Re: HTTP router point-of-view concerns Poul-Henning Kamp
Re: HTTP router point-of-view concerns Michael Sweet
Re: HTTP router point-of-view concerns Christian Parpart
Re: HTTP router point-of-view concerns Willy Tarreau
Re: HTTP router point-of-view concerns Patrick McManus
Re: HTTP router point-of-view concerns Jeff Pinner
Re: HTTP router point-of-view concerns Martin Thomson
Re: HTTP router point-of-view concerns Roberto Peon
Re: HTTP router point-of-view concerns Ludin, Stephen
Re: HTTP router point-of-view concerns Roberto Peon
Re: HTTP router point-of-view concerns James M Snell
Re: HTTP router point-of-view concerns Amos Jeffries
Re: HTTP router point-of-view concerns Amos Jeffries
Re: HTTP router point-of-view concerns Roberto Peon
Re: HTTP router point-of-view concerns Yoav Nir
Re: HTTP router point-of-view concerns Willy Tarreau
Re: HTTP router point-of-view concerns Poul-Henning Kamp
Re: HTTP router point-of-view concerns Poul-Henning Kamp
Re: HTTP router point-of-view concerns Willy Tarreau
Re: HTTP router point-of-view concerns Poul-Henning Kamp
Re: HTTP router point-of-view concerns Sam Pullara
Re: HTTP router point-of-view concerns Willy Tarreau
Re: HTTP router point-of-view concerns Mark Delany
Re: HTTP router point-of-view concerns Poul-Henning Kamp
Re: HTTP router point-of-view concerns Poul-Henning Kamp
Re: HTTP router point-of-view concerns Willy Tarreau
Re: HTTP router point-of-view concerns Willy Tarreau
Re: HTTP router point-of-view concerns Poul-Henning Kamp
Re: HTTP router point-of-view concerns Willy Tarreau
Re: HTTP router point-of-view concerns Yoav Nir
Re: HTTP router point-of-view concerns Poul-Henning Kamp
Re: HTTP router point-of-view concerns Poul-Henning Kamp
Re: HTTP router point-of-view concerns Yoav Nir
Re: HTTP router point-of-view concerns Willy Tarreau
Re: HTTP router point-of-view concerns Poul-Henning Kamp
Re: HTTP router point-of-view concerns Stephen Farrell
Re: HTTP router point-of-view concerns Willy Tarreau
Re: HTTP router point-of-view concerns Sam Pullara
Re: HTTP router point-of-view concerns Nicolas Mailhot
Re: HTTP router point-of-view concerns Nicolas Mailhot
Re: HTTP router point-of-view concerns Nicolas Mailhot
Re: HTTP router point-of-view concerns Martin Nilsson
Re: HTTP router point-of-view concerns Nico Williams
Re: HTTP router point-of-view concerns Nico Williams
Re: HTTP router point-of-view concerns Poul-Henning Kamp
Re: HTTP router point-of-view concerns Nico Williams
Re: HTTP router point-of-view concerns Poul-Henning Kamp
Re: HTTP router point-of-view concerns Nico Williams