Skip to Content.
Sympa Menu

per-entity - Re: [Per-Entity] remaining BIG questions

Subject: Per-Entity Metadata Working Group

List archive

Re: [Per-Entity] remaining BIG questions


Chronological Thread 
  • From: Tom Scavo <>
  • To: "Cantor, Scott" <>
  • Cc: Tom Scavo <>, Nick Roy <>, Per-Entity Metadata Working Group <>
  • Subject: Re: [Per-Entity] remaining BIG questions
  • Date: Wed, 14 Sep 2016 16:02:55 -0400
  • Ironport-phdr: 9a23:E7nJwBIZQx/GIQAwMdmcpTZWNBhigK39O0sv0rFitYgXI/rxwZ3uMQTl6Ol3ixeRBMOAtKIC1rGd6v2ocFdDyKjCmUhKSIZLWR4BhJdetC0bK+nBN3fGKuX3ZTcxBsVIWQwt1Xi6NU9IBJS2PAWK8TWapAQfERTnNAdzOv+9WsuL15z2hKiO/MiZSAxOmD2nJftJJxKqsU+Z4sIfh5dlMOBr4hzSvz1Fd/kAlk1yIlfGoxH5rvy79YBku3BMoekq/tBHeaT8Y6kiS7FEVnIrP31jt56jjgXKUQbavihUaW4RiBcdRlGdtBw=

On Wed, Sep 14, 2016 at 3:47 PM, Cantor, Scott
<>
wrote:
> On 9/14/16, 3:05 PM,
> "
> on behalf of Tom Scavo"
> <
> on behalf of
> >
> wrote:
>>
>> Today we deal with that in documentation: "It is strongly recommended
>> that InCommon SPs and IdPs refresh and verify metadata at least daily.
>> An optimal configuration would attempt to refresh metadata every hour
>> (assuming your client supports HTTP Conditional GET)."
>
> In both the batch and MDQ cases, our metadata code will allow cacheDuration
> to influence the behavior, so if you want people to refresh every hour, you
> can set cacheDuration to cause that to happen, within some boundaries the
> deployer can set. You don't have to just rely on advice.

Yes, I get that. That's why I'm asking this group if it matters. I'm
not sure it does but I could be missing something.

In the case of aggregates, cacheDuration and HTTP Conditional GET go
together. For entities, HTTP Conditional GET is a "nice to have," as
you suggested earlier, since the penalty for refreshing the cache is
much less for small files.

Tom



Archive powered by MHonArc 2.6.19.

Top of Page