W3C home > Mailing lists > Public > public-webid@w3.org > October 2017

Re: What is an "up to date" version?

From: Story H.J. <H.J.Story@soton.ac.uk>
Date: Sun, 29 Oct 2017 07:19:49 +0000
To: "Ed - 0x1b, Inc." <w3c@0x1b.com>
CC: public-webid <public-webid@w3.org>
Message-ID: <D43A5464-D7C2-46ED-968D-AA672C4657C5@soton.ac.uk>

On 29 Oct 2017, at 03:11, Ed - 0x1b, Inc. <w3c@0x1b.com<mailto:w3c@0x1b.com>> wrote:

I would guess an up to date etag is typical for cache freshness.

close. The Etag won't tell the local cache if it needs to update the version, it will
just be useful when making a request to ask for one where intermediary caches
can say, nothing has changed since you last looked.

Look at



On Sat, Oct 28, 2017 at 2:10 PM, Martynas Jusevičius
<martynas@atomgraph.com<mailto:martynas@atomgraph.com>> wrote:

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."

The phrase "up to date" is repeated multiple times later on, but not defined

So what is it and who decides that -- the implementor? For how long am I
supposed to safely cache the graphs?


Received on Sunday, 29 October 2017 07:21:24 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:06:03 UTC