Re: Cache revalidations

Lets try to separate information required for proper HTTP operation and
information required for good removal policy implementations. These are
different, and have different requirements on persistense.

The fact that these are fully mixed in the current implementation does
not say they should be. There is a long running and valid discussion on
how storage of policy data should be implemented. The current
implementation is far from the best.

Regards
Henrik

Andres Kroonmaa wrote:
>
> On 8 Oct 2001, at 12:38, Henrik Nordstrom <hno@squid-cache.org> wrote:
>
> > To conclude, the store API needs an interface for updating the objects
> > Date and Expires header in a permanent manner.
>
> Or more generally, StoreEntry storeSwapLogData, or any Metadata.
> Updating refcount on the way would be lovely. Possibly some other
> useful metric we might want to add sometime (RTT to origin for eg).
>
> ------------------------------------
> Andres Kroonmaa <andre@online.ee>
> CTO, Microlink Online
> Tel: 6501 731, Fax: 6501 725
> Pärnu mnt. 158, Tallinn,
> 11317 Estonia
Received on Mon Oct 08 2001 - 09:13:56 MDT