FileBackedHTTPMetadaProvider fetch/refresh frequency determined by ?

[Baron Fujimoto]

On Sat, Dec 10, 2011 at 02:31:45AM +0000, Cantor, Scott wrote:
: On 12/9/11 8:55 PM, "Baron Fujimoto" <baron at hawaii.edu> wrote:
: 
: >Since we aren't explicitly setting maxRefreshDelay, I assume it should be
: >using its default value of 4H, but the timestamp on the saved metadata
: >file indicates that it appears to be saved/refreshed just once daily.
: >What
: >am I missing that determines the frequency that the metadata file is
: >saved or refreshed for this MetadataProvider?
: 
: Nothing; I have the same thing, with no non-default value.
: 
: Mine checks every 3 hours or so, per the factor applied to the 4 hour
: interval, and updates whenever the file gets reposted in the afternoon and
: it checks.

Ah, so it's checking for updates with frequency
(maxRefreshDelay * refreshDelayFactor), but only actually downloading the
data if it has been updated remotely (InCommon reposting the metadata
daily)?  Thanks for clearing that up.

How does Shib figure whether the remote metadata has been updated?  Is
it determining that from the metadata itself?  E.g. I see a timestamps in
the InCommon metadata "INC20111212T194600" or something else (diff with
current local saved copy?)

-- 
Baron Fujimoto <baron at hawaii.edu> :: UH Information Technology Services
minutas cantorum, minutas balorum, minutas carboratum desendus pantorum