HTTP Client Attributes

[Cantor, Scott]

On 5/3/18, 4:33 PM, "Tom Scavo" <trscavo at gmail.com> wrote:

> And that request will be an HTTP conditional request, right? 

No.

> The downside is, when httpCaching="none", it always goes out to the network.

No. There's *no* HTTP caching implemented by the dynamic code, it's left to the client bean. The batch providers have done a limited conditional GET form of caching for a while, independent of the client bean, they just don't physically cache response bodies in the HTTP sense.

The dynamic providers always decide whether to "try to get something new" and if they do, and the back-end is HTTP, then it just asks the client to issue a GET. What happens then is up to the client.

> For FileBackedHTTPMetadataProvider, I don't see a use for
> httpCaching="memory", except perhaps for individual entity
> descriptors. Which reminds me, is there a way to batch load a bunch of
> individual entity descriptors? The use case is pre-loading of
> high-value entities.

LocalDynamic can do that, effectively, if not explicitly.

-- Scott