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: David Walker <>
  • To: Tom Scavo <>
  • Cc: Per-Entity Metadata Working Group <>
  • Subject: Re: [Per-Entity] implementing a cache on the client
  • Date: Fri, 5 Aug 2016 10:13:17 -0700
  • Authentication-results: spf=none (sender IP is ) ;
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:99

Agreed.  I was just trying to capture the sentiment of the discussion.  We'll dot i's, cross t's, and craft good language when we write our report.

David


On 08/05/2016 10:00 AM, Tom Scavo wrote:
On Fri, Aug 5, 2016 at 12:40 PM, David Walker  wrote:
It should not be overly difficult or costly for a federation to run the
entire per-entity infrastructure for its members.
Well, I think the sentiment is correct but different words are needed.
For one thing, it *will* be difficult and costly, otherwise we would
have done it already. Also, the phrase "entire per-entity
infrastructure" is confusing when taken out of context.

I think the point you're trying to make is: All that's needed on the
client side is a standard MDQ client (i.e., a client that conforms to
the MDQ protocol). InCommon will provide a complementary MDQ server
with the following features...

Tom

Attachment: signature.asc
Description: OpenPGP digital signature




Archive powered by MHonArc 2.6.19.

Top of Page