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: Jorj Bauer <>, "" <>
  • Subject: Re: [Per-Entity] implementing a cache on the client
  • Date: Wed, 27 Jul 2016 18:06:13 +0000
  • Accept-language: en-US
  • Authentication-results: spf=pass (sender IP is 164.107.81.222) 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, 1:56 PM,
"
on behalf of Jorj Bauer"
<
on behalf of
>
wrote:
>
> Sure, and DNS has the same characteristics.

DNS can tolerate long outages? That is really not my experience, but I'm no
DNS expert. Can you clarify?

> It's easy enough to configure a server to use a locally installed DNS
> caching server, and
> I would hope to be able to do the same with an MDQ server as an
> intermediate cache.

Would you disagree that that would be a very much minority view?

It should be self-evident that you *can* do this, this is HTTP, it's designed
for proxying, caching, etc. I'm just not at all convinced most people would
or that this would be the way to think about the problem.

-- Scott



Archive powered by MHonArc 2.6.19.

Top of Page