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: Thomas Lenggenhager <>, Nick Roy <>, "" <>
  • Subject: RE: [Per-Entity] implementing a cache on the client
  • Date: Thu, 4 Aug 2016 14:23:36 +0000
  • Accept-language: en-US
  • Authentication-results: spf=pass (sender IP is 164.107.81.212) 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
> If our experience with Duo Security is any indicator, there is a
> significant fraction of deployments that care about outages of cloud
> services. This has been discussed (with the community) many times. The
> same concerns will surface in the case of per-entity metadata
> distribution.

That doesn't generally translate into "sure, I'll do work".

> I'm afraid you can't ignore per-entity metadata distribution. We know
> what will happen if deployments continue to rely on aggregates.

We know, but they will simply ignore the problem until it breaks.

-- Scott


Archive powered by MHonArc 2.6.19.

Top of Page