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

Re: Submitted new I-D: Cache Digests for HTTP/2

From: Martin Thomson <martin.thomson@gmail.com>
Date: Tue, 2 Feb 2016 13:54:42 +1100
Message-ID: <CABkgnnXvarr75QtsYoqAsfoWfwajqYVSqMMC8qNG2eSgshuMUg@mail.gmail.com>
To: Kazuho Oku <kazuhooku@gmail.com>
Cc: Eliezer Croitoru <eliezer@ngtech.co.il>, HTTP Working Group <ietf-http-wg@w3.org>
On 2 February 2016 at 12:45, Kazuho Oku <kazuhooku@gmail.com> wrote:
>> From my point of view and understanding a cache-digest will probably require
>> some per client "cache-digest dictionary" which can cause some issues to
>> systems\servers with lots of clients\connections. The other side would be
>> the ongoing re-validation and maintenance of this dictionaries.
> That is a fair argument.  However, servers are already required to
> maintain such dictionary for HTTP/2 (i.e. HPACK).

Note that a server would not be required to support cache-digest.  It
can ignore it entirely and push willy-nilly.  Or it can use the extra
information as it appears to optimize.  Also, contrary to what is
implied here, you don't need to maintain this as extra state if you
are happy to consume the header field on every request.
Received on Tuesday, 2 February 2016 02:55:12 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 22 March 2016 12:47:11 UTC