Qs after reviewing Java dynamic metadata resolvers

[Cantor, Scott]

> Well, maybe I'm wrong but I thought the only reason it does that is because
> the underlying HTTP client lib doesn't natively support caching and
> conditional GET.  Apache HttpClient does and it feels more natural to me to
> leave conditional GET at that layer.

True, but if the client did it but not across restarts, that wouldn't have been sufficient. That's the gap, though it's specific to the batch resolver.

> There is the issue that the file-based HttpClient cache doesn't persist across
> restarts, by conscious intent.  We did briefly discuss possibly changing that,
> maybe as a configurable option.  I'm not opposed.  However, since we're
> now going to implement a "SAML cache" that persists across restarts, I think
> doing that has less value now, at least for the dynamic resolver restart case.

No, it's a batch thing, but it is a thing, and we still do have work to do there to optimize the startup time. If the solution is changing the cache persistence, that's ok.

-- Scott