preloading high-value entity metadata

[Tom Scavo]

On Wed, May 16, 2018 at 12:46 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:
>> If I follow this thread (I've been elsewhere) you need the
>>       persistentCacheManagerRef
>>       persistentCacheManagerDirectory
>>       persistentCacheKeyGeneratorRef
>>       initializeFromPersistentCacheInBackground
>>       initializationFromCachePredicateRef
>>       backgroundInitializationFromCacheDelay
>>
>> attributes.  As per [1].  This gives you control of how, where, and what is
>> cached and what and when is reloaded.
>
> Yeah, that's it.

Yes, I know about the persistent cache but that's not what I was
asking about. AFAIK, that cache only affects the startup process (like
the backing file on FileBackedHTTPMetadataProvider).

Please take a look at Example 4 on the ChainingMetadataProvider page.
[1] That example uses FileBackedHTTPMetadataProvider to short-circuit
a DynamicHTTPMetadataProvider. Is that something we want to document,
and if so, how can it be generalized? (I'm pretty sure the answer to
the latter question is that it can't be generalized, at least not with
what we have available to us now.)

Thanks,

Tom

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