Dynamic metadata resolver; HttpClient usage

[Cantor, Scott]

On 11/19/14, 12:52 AM, "Brent Putman" <putmanb at georgetown.edu> wrote:


>
>The dynamic metadata resolver and associated IdP Spring schema and config 
>is essentially done.  It might be a good idea if someone other than me 
>gives the IdP config schema a look over (shibboleth-metadata.xsd) and the 
>parsers, just to have another opinion
> what it should look like, etc.  Or in case I've totally missed something 
>that is expected to be there.

I'll try and take a look tomorrow.

>Somewhat related: HttpClient usage.  I didn't see (point me if I'm 
>missing) that we are by default wiring in any particular HttpClient 
>instance into components, and in particular I'm wondering about use of 
>caching HttpClients.  Should we either wire one of those in and/or make 
>the parsers, etc build a caching variant by default?  Basically: should 
>HttpClient caching be opt-in, or opt-out?

Opt-out I would think.

>Having it be on by default might be nice for deployers, but would mean 
>that we'd have to decide upon the caching strategy/store (essentially 
>in-memory vs filesystem), so I don't know how contentious that choice 
>would be...

Is it storing the data or just the caching tags?

-- Scott