reconciling the Reloading Attributes with the Dynamic Attributes

[Tom Scavo]

I'm trying to reconcile the Reloading Attributes with the Dynamic
Attributes on a metadata provider. [1] Basically I have two questions:

1) What is the effect of the metadata's @cacheDuration attribute on
the operation of a reloading provider (such as the
FileBackedHTTPMetadataProvider)?

2) What is the effect of the metadata's @validUntil attribute on the
operation of a dynamic provider (such as the HTTPMetadataProvider)?

The answer to the first question would appear to be "none" since a
FileBackedHTTPMetadataProvider is a non-caching metadata provider. Is
this correct?.

The answer to the second question depends on the value of the
requireValidMetadata attribute but why then is the
expirationWarningThreshold attribute confined to the reloading
attributes?

Thanks,

Tom

[1] https://wiki.shibboleth.net/confluence/x/8YAOAQ