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: Thomas Lenggenhager <>, Nick Roy <>
  • Cc: "" <>
  • Subject: RE: [Per-Entity] implementing a cache on the client
  • Date: Thu, 4 Aug 2016 13:53:18 +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

> Open this directory structure for access via rsync, Dropbox, OwnCloud,
> 'you name it' to sync the signed files to campuses operating their own
> local MDQ server to get independent from the centrally operated MDQ. No
> need for HTTP proxies, just for local MDQ servers at the campuses.

Right, but how many campuses will want to do that? How many will bother? How
many will ignore the whole issue because they're being told that moving to
this new approach suddenly requires extra work from them?

The group consenus was that while nothing we do should or will make that
approach difficult for people to implement, we shouldn't focus on it as a
workaround for delivering a reliable service.

All that said, the Dropbox idea is a good one. Why not piggyback on existing
cloud services? I like it.

-- Scott




Archive powered by MHonArc 2.6.19.

Top of Page