Re: HPACK encoder/decoder memory bounding from Fred Akalin on 2013-10-25 (ietf-http-wg@w3.org from October to December 2013)

From: Fred Akalin <akalin@google.com>
Date: Fri, 25 Oct 2013 16:17:20 -0700
To: Martin Thomson <martin.thomson@gmail.com>
Cc: Mike Bishop <Michael.Bishop@microsoft.com>, Tatsuhiro Tsujikawa <tatsuhiro.t@gmail.com>, Hervé Ruellan <ruellan.crf@gmail.com>, Osama Mazahir <OSAMAM@microsoft.com>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <CANUYc_TBgmdFXKQwHyr9JnTsd4gSbAmNkryPnNSrm4UTk4VmdA@mail.gmail.com>

What about something like: "Each endpoint has its own set of settings
values, but also keeps track of its peer's set. An endpoint sends a
SETTINGS frame to inform the other endpoint of changes to its set."

A bit wordy, I guess.

On Fri, Oct 25, 2013 at 1:33 PM, Martin Thomson <martin.thomson@gmail.com>wrote:

> On 25 October 2013 12:45, Mike Bishop <Michael.Bishop@microsoft.com>
> wrote:
> > That introduces a new confusion around "apply" -- the setting I send
> reflects my expectation of your behavior.
>
> Yes, the setting I send is about me, but it constrains your behaviour.
>
> Maybe that's what I need to say...
>

Received on Friday, 25 October 2013 23:17:47 UTC