Re: Alt-Svc alternative cache invalidation (ext#16)

• From: Martin Thomson <martin.thomson@gmail.com>
• Date: Mon, 18 Aug 2014 10:42:29 -0700
• To: Erik Nygren <erik@nygren.org>
• Cc: HTTP Working Group <ietf-http-wg@w3.org>
• Message-ID: <CABkgnnXRw7Rc7MJddW4UqSo2=hQ2E2EysLyzcaVM6_xf7h0R9g@mail.gmail.com>

On 18 August 2014 10:37, Erik Nygren <erik@nygren.org> wrote:
> Would it make more sense for (origin) to be the key with a set of (service
> protocol, service endpoint) tuples being the value?  This allows a reset or
> correction (or removal?) by publishing a new set of [(service protcol,
> service endpoint), ...] values.

The problem is that there are two different ways to update the set:

* The Alt-Svc header field bears multiple values and could be used in
the fashion you describe.

* The ALTSVC frame type bears just a single value.

The latter is the problem here.

Received on Monday, 18 August 2014 17:42:56 UTC