per-entity - Re: [Per-Entity] splitting the aggregate
Subject: Per-Entity Metadata Working Group
List archive
- From: "Walter Forbes Hoehn (wassa)" <>
- To: Tom Scavo <>
- Cc: Per-Entity Metadata Working Group <>
- Subject: Re: [Per-Entity] splitting the aggregate
- Date: Mon, 8 Aug 2016 14:51:40 +0000
- Accept-language: en-US
- Authentication-results: spf=none (sender IP is ) ;
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
If an SP-only aggregate were available, I’d certainly make use of it
immediately. I agree with Ian in terms of the potential for a move like this
to negatively impact MDQ adoption in the short term. A related concern is the
possible perception, with an announcement of this change just prior to
announcements related to MDQ, that we are just throwing things against the
wall to see what sticks. I guess that comes down to how/whether the new
aggregate is advertised.
-WFH
> On Aug 7, 2016, at 4:36 PM, Tom Scavo
> <>
> wrote:
>
> As an interim measure (while per-entity metadata distribution is
> spinning up), some folks have suggested that Ops split the main
> InCommon aggregate into smaller SP and IdP aggregates and distribute
> each separately. Is such a strategy advisable?
>
> Tom
- [Per-Entity] splitting the aggregate, Tom Scavo, 08/07/2016
- RE: [Per-Entity] splitting the aggregate, Cantor, Scott, 08/08/2016
- Re: [Per-Entity] splitting the aggregate, Ian Young, 08/08/2016
- Re: [Per-Entity] splitting the aggregate, Walter Forbes Hoehn (wassa), 08/08/2016
- Re: [Per-Entity] splitting the aggregate, Nick Roy, 08/08/2016
- <Possible follow-up(s)>
- [Per-Entity] Splitting the Aggregate, Tom Scavo, 08/30/2016
Archive powered by MHonArc 2.6.19.