SP V3 metadata types

[Cantor, Scott]

> The current implementation of DynamicHTTPMetadataProvider caches entity
> metadata in a local directory (if persistentCacheManagerDirectory is specified)
> but then the cache is treated as nothing more than a glorified backing file (at
> least AFAICT). The provider needs to be smarter about how it leverages cached
> metadata.

I agree, but I'm not sure your idea of "smarter" matches mine, I just asked for some particular caching and change detection improvements and I think they're underway. They aren't attempts to turn "remote" into "local". People don't cache DNS that way, and this is the same, you either trust a remote source or you're paranoid (possibly for good reason) and want to do it all yourself, in which case you can just script up your own folder to taste and use LocalDynamic. I don't think there's sufficient demand for us to bother with that. I think we implemented (or have in progress) all the improvements that were suggested by the InCommon WG).

> At this point, I'm tempted to dive into a number of "what ifs" but that would
> probably be premature since (as you say) some modifications are coming. I
> hope I'm watching the relevant jira issues. Can/should we discuss it here
> instead?

JIRA isn't good for long side discussions, so if there's something not in JIRA that you think you want done, I would take it up here with Brent, because I'm not going to be the one implementing it anyway. The issues I had I filed and they're fairly limited in scope.

-- Scott