Skip to Content.
Sympa Menu

per-entity - Re: [Per-Entity] distribution of aggregate metadata

Subject: Per-Entity Metadata Working Group

List archive

Re: [Per-Entity] distribution of aggregate metadata


Chronological Thread 
  • From: Scott Koranda <>
  • To: "Cantor, Scott" <>
  • Cc: Tom Scavo <>, "Walter Forbes Hoehn (wassa)" <>, Nick Roy <>, Chris Phillips <>, Per-Entity Metadata Working Group <>
  • Subject: Re: [Per-Entity] distribution of aggregate metadata
  • Date: Thu, 11 Aug 2016 15:16:40 -0500
  • Ironport-phdr: 9a23:vnF5iBD3gLbI/3e+l0KIUyQJP3N1i/DPJgcQr6AfoPdwSP3yoMbcNUDSrc9gkEXOFd2Crakb26yL6Ou5BCQp2tWojjMrSNR0TRgLiMEbzUQLIfWuLgnFFsPsdDEwB89YVVVorDmROElRH9viNRWJ+iXhpRZbIBj0NBJ0K+LpAcaSyp3vj6Hhs6HUNk9jjTyhZqk2ZC69qhnN/IFCioJkNqErjEHhpWBVPela2DU7C0iUmkPH7cCs4NZA9D5Zvf4ov5pbUqLgdqI0RJRXCT0nNyY+48i95kqLdheG+nZJCjZeqRFPGQWQqUiiBpo=

> > b) periodically downloading an aggregate that contains all of
> > the entities (since we expect aggregates to stay around for
> > some time) and writing it to the side on disk but not using it
> > except when detecting that MDQ queries are failing (hence not
> > having to take up memory when not necessary).
>
> No, apart from discovery-motivated necessities, but not for basic use, no.

Again, to be pedantic:

Is your argument that the extra costs for the Shibboleth team
and the complexity of such a design outweigh the perceived
benefit of being able to load metadata for a "not-recently
required entity" during a MDQ service outage?

Thanks,

Scott K




Archive powered by MHonArc 2.6.19.

Top of Page