Skip to Content.
Sympa Menu

per-entity - Re: [Per-Entity] implementing a cache on the client

Subject: Per-Entity Metadata Working Group

List archive

Re: [Per-Entity] implementing a cache on the client


Chronological Thread 
  • From: "Cantor, Scott" <>
  • To: Tom Scavo <>
  • Cc: "" <>
  • Subject: Re: [Per-Entity] implementing a cache on the client
  • Date: Wed, 27 Jul 2016 19:33:09 +0000
  • Accept-language: en-US
  • Authentication-results: spf=pass (sender IP is 164.107.81.214) smtp.mailfrom=osu.edu; incommon.org; dkim=none (message not signed) header.d=none;incommon.org; dmarc=bestguesspass action=none header.from=osu.edu;
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:99

On 7/27/16, 3:20 PM,
"
on behalf of Tom Scavo"
<
on behalf of
>
wrote:

> What's the difference? I'm talking about HTTP 304, not HTTP 404.

Well, one is an error, one is not.

> You are absolutely correct but I claim a two-week outage of the
> aggregates served from md.incommon.org has probability zero.

And I claim a two week outage of an MDQ service is pretty much also
probability zero. Still not getting it. I really just missed the point of the
example.

> From where I sit, aggregate distribution and per-entity distribution
> are like apples and oranges.

I do understand that one can tolerate outages that are an order of magnitude
larger, but in terms of fundamental requirements, they're both potentially a
highly redundant web presence serving static documents. That's apples and
some other more expensive kind of apples to me.

But I seem to be in the minority on this, so maybe we could focus this
discussion on your original subject line. What exactly do people need us to
implement? At minimum, on-disk cache, clearly.

-- Scott





Archive powered by MHonArc 2.6.19.

Top of Page