Re: Recovery from decompression failure (was: Re: Cost analysis: (was: Getting to Consensus: CONTINUATION-related issues))

2014/07/24 2:12 "Martin Thomson" <martin.thomson@gmail.com>:
>
> On 22 July 2014 17:50, Tatsuhiro Tsujikawa <tatsuhiro.t@gmail.com> wrote:
> > We need to also clarify when first header table size change applies: a)
> > reception of SETTINGS (and its ACK) or b) encoding context update.
> > My understanding is a). The receiver of SETTINGS processes the setting
> > values in the order they appear in a frame and shrinking header table
size
> > necessary. Then it can send encoding context update only for last seen
table
> > size value.  This is possible because receiver of SETTINGS ACK also
applies
> > its pending settings in the same way.  It then validates the received
> > encoding context update against last seen value and applies table size
> > again.  This is simpler than multiple encodong context update because we
> > just renember and validate 1 value instead of 2.
>
>
> Have a look at the text that I proposed on this
> (Received on Thursday, 24 July 2014 00:56:20 UTC

Follow Lee on X/Twitter - Father, Husband, Serial builder creating AI, crypto, games & web tools. We are friends :) AI Will Come To Life!

Check out: eBank.nz (Art Generator) | Netwrck.com (AI Tools) | Text-Generator.io (AI API) | BitBank.nz (Crypto AI) | ReadingTime (Kids Reading) | RewordGame | BigMultiplayerChess | WebFiddle | How.nz | Helix AI Assistant