- From: Ed - 0x1b, Inc. <w3c@0x1b.com>
- Date: Sat, 28 Oct 2017 19:11:56 -0700
- To: public-webid <public-webid@w3.org>
I would guess an up to date etag is typical for cache freshness. https://en.wikipedia.org/wiki/HTTP_ETag On Sat, Oct 28, 2017 at 2:10 PM, Martynas Jusevičius <martynas@atomgraph.com> wrote: > Hi, > > I'm implementing a cache for WebID graphs to improve performance. I was > looking at WebID-TLS 4.1 Authentication sequence, which says: > "If the WebID Verifier has an up to date version of the graph in its graph > cache then it can return it." > https://dvcs.w3.org/hg/WebID/raw-file/tip/spec/tls-respec.html#authentication-sequence > > The phrase "up to date" is repeated multiple times later on, but not defined > anywhere. > > So what is it and who decides that -- the implementor? For how long am I > supposed to safely cache the graphs? > > > Martynas > atomgraph.com
Received on Sunday, 29 October 2017 02:13:09 UTC