Re: CL Scaling for High Traffic Web Sites

My experience, based on having worked at a significantly large site
was that the best approach by far was to a customised traditional web
cache (a distributed squid in some form or other) to cache everything
that could "easily" be cached. This typically is more than 90% of
your traffic...

Just curious, how does squid refresh its cache? Is it possible for
the web server to tell it to expire an url explicitly? This could be
useful if the site uses predictable url (eg. a REST interface) to
manage user data.

.