DynamicHTTPMetadataProvider

[Cantor, Scott]

> I suppose one way to support both schemes (or indeed arbitrarily many)
> would be: Instead of having just one strategy, have multiple ones, in some
> preference order.  When resolving, loop over them in order until you find a
> match.  I'll give that some thought also. Assuming it's feasible, that doesn't
> actually address though what the default one(s) should be.

I think there's a separate problem, due to artifact usage (I'll admit that it's an edge case, but just go with it). If the algorithm is to walk the tree to index what's in the directory, then you can do an in-memory index and dual-index by hash and entityID. But if the idea is to ignore what's actually there and just compute requests on-demand, you can't do that on the IdP's end by entityID since you might only have the source ID of an artifact. Using the hash as the name gets you both at once.

The MDA isn't trying to solve that problem, isn't it the thing *producing* the files in the directory?

-- Scott