On Jun 2, 7:18am, Reuben Farrelly (possibly) wrote:
> I guess one of the more important points to note is that for many if not
> most people, Squid is used primarily to *save* bandwidth and therefore
> cost. Although the approach of "intelligent fetching" may be beneficial
> for speed, it would probably not be of any benefit in terms of bandwidth
> saving because guessing invariably is a risky process [you don't know for
> sure if the object will be retrieved by the clients]. I personally
> consider the "bandwidth saving" ideas behind squid to be of more importance.
Certainly. That's one of the points behind the below idea - the client
is almost certainly going to make the request anyway.
> At Wednesday 2/06/99 04:32 AM -0400, Allen Smith wrote:
> >A minor version of this that wouldn't be nearly as hard to implement
> >(I've looked at doing it myself, although it's currently pretty far
> >down on my ever-growing list of tasks) would be requesting and caching
> >any cachable referred object (referred via HTTP responses, not HTML
> >coding).
-Allen
-- Allen Smith easmith@beatrice.rutgers.eduReceived on Fri Jun 04 1999 - 19:58:01 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:46:44 MST