Re: Squid store replacement policies

Terence Kelly wrote:
>
> Regarding the design of this aspect of the API, you might want to
> check out the following book:
>
> _C Interfaces and Implementations_
> by David R. Hanson
> Addison-Wesley Professional Computing Series, 1997
> ISBN 0-201-49841-3
> http://www.cs.princeton.edu/software/cii/
>
> This book addresses several of the issues you've been discussing,
> e.g., mapping a function onto all elements in a "container" while
> enforcing the requirement that the container not change during this
> operation.
>
> Hanson's book doesn't solve the exact problems you face, but it may
> be a source of inspiration, particularly Chapter 7.

Thanks. I'll check it out. However, for this particular API we already
have all the mapping we need I would say. I am only talking about
abstracting functionality that already exists in Squid today, and this
is quite a quite well defined scope (for the time being at least).

--
Henrik Nordstrom
Squid hacker