Staggering the MetadataProvider reloadInterval

[Scott Klawitter]

Thanks for the reply Scott,

I should have mentioned that the MetadataProvider type="Chaining". 

I was referring to staggering the reloadInterval for each chained
MetadataProvider.

The reason: Federations like the UKfederation take a long time to
download the metadata. I wasn't sure if this had an effect on
performance of the SP processing requests.

<MetadataProvider type="Chaining">
  <MetadataProvider type="XML"
                    uri="https://federationa.com/metadata.xml"
                    backingFilePath="
prod-country1-federationa-metadata.xml "
                    reloadInterval="7200">
  </MetadataProvider>
  <MetadataProvider type="XML"
                    uri="https://federationb.com/metadata.php"
 
backingFilePath="prod-country2-federationb-metadata.xml"
                    reloadInterval="180000">
  </MetadataProvider>
</MetadataProvider>

Is there a suggested reloadInterval value to use for an SP?

Thank you,

- Scott K


-----Original Message-----
From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net]
On Behalf Of Cantor, Scott
Sent: Tuesday, October 25, 2011 2:59 PM
To: users at shibboleth.net
Subject: Re: Staggering the MetadataProvider reloadInterval

On 10/25/11 3:46 PM, "Scott Klawitter" <sklawitter at ebsco.com> wrote:

>Does anyone know if there is a performance gain by staggering the 
>MetadataProvider reloadInterval in the shibboleth2.xml configuration
file.

Staggering it against what?

> 
>What value is a standard best practice for an SP.

The reload interval is a function of the source of the metadata and how
often you expect it to change. The cost of checking is near zero anyway
as long as the server returns a 304 when it should.

-- Scott

--
To unsubscribe from this list send an email to
users-unsubscribe at shibboleth.net