Mark, I'm stalking your latest edits of this draft in Github and it's looking good. I particularly like the inclusion of Etags. A server should be able to use those etags to decide if it needs to push something new, although there is no way to do that *right now*. Is there a document (besides the HTTP/2 RFC, which is a bit vague on this) detailing the workflows with pushed representations, particularly what the browser is expected to do? On Tue, May 31, 2016 at 7:24 AM, Mark Nottingham <mnot@mnot.net> wrote: > > > On 15 May 2016, at 1:43 AM, Martin Thomson <martin.thomson@gmail.com> > wrote: > > > >> From small to large: > > > > Nit: > > 2. If "W" and "V" are equal, continue to the next "V". > > > > This should be next "W", I think. > > There is no next W... > > > > I think that Q would be better encoded as a series of 0 bits followed > > by a 1 bit. The reason I say that is that it is (marginally) easier > > to generate the values then by masking in the R value in the right > > place in a freshly calloc'd piece of memory. > > I'm not fussed; Kazuho? > > > > This document really needs to describe what the contents of the cache > > digest are, and to describe how to decode the cache digest. Without > > defining what it means to receive and decode this information, this > > specification almost says nothing at all. > > Whatever happened to "left as an exercise to the reader?" > > :) > > Yes, we do. > > Cheers, > > > -- > Mark Nottingham https://www.mnot.net/ > > >
Received on Tuesday, 31 May 2016 06:20:08 UTC