[squid-dev] The next step towards: StoreID and metalink.

[Alex Rousskov]

On 09/19/2015 05:28 PM, Eliezer Croitoru wrote:

> There are things which can help an ECAP module to decide how to do
> things when handling metalinks related affairs.
> For example, a cache object lookup from within an ECAP module.
> So basically the logic of the ECAP module is 100% blind to the cache
> internals.

FWIW, there have been requests to expose host cache state to eCAP
adapters. It can be easily done (via Cache-Lookup metadata) for the
current request [in pre-cache REQMOD]. Doing so will even be compatible
with ICAP services.

Unfortunately, but most real use cases I know about actually need a true
"cache lookup using an arbitrary request and/or StoreID" functionality
and not just a "is the current request likely to be served from cache?"
answer. Supporting arbitrary lookups would require expanding eCAP API. I
would support such expansion, especially if we have several different
specific use cases the back the new API design up.

Alex.