reconciling the Reloading Attributes with the Dynamic Attributes

[Cantor, Scott]

> Thanks, that makes sense. Is the same true in the case of a dynamic
> provider? If so, why are the attributes called
> minRefreshDelay/maxRefreshDelay in the one case and
> minCacheDuration/maxCacheDuration in the other?

I believe the dynamic ones don't refresh per se, they just dump their cached data or mark it to indicate a new copy should be fetched. The names seem to match that to me, so I think they're fine.

> Btw, note that the refreshDelayFactor attribute has exactly the same
> description in both cases. That description really only makes sense for a
> reloading provider. In the case of a dynamic provider, the description is very
> confusing.

It's doing the same thing, modifying the caclulated value that governs how often it refreshes, it's just the underlying mechanics that are a bit different. I'm sure the text is just a cut and paste.

> I believe you. The point I'm trying to make is that httpCaching="none"
> in the case of FileBackedHTTPMetadataProvider is an apparent contradiction.

It isn't, but then I know what the code is doing.

-- Scott