Re: an idea for next generation APT archive caching

[Tobias Hertkorn]

One bad thing (amongs others) that happens if you use squid - first of all 
you have to make your clients use the proxy settings AND way more imortant - 
a request for http://yourserver/testing/..../apache....deb will not create a 
hit if requested as http://yourserver/sid/..../apache...deb . Furthermore 
requests to similar mirrors will not create cache hits. So everybody has to 
use the same sources list, down to the same requests by symlinks.
You can make squid better than the default, but excellent for clients that 
are not owned by the very same admin? I doubt it.

Greets,
Tobi
----- Original Message ----- 
From: "Robert Collins" <[EMAIL PROTECTED]>
To: "Chris Halls" <[EMAIL PROTECTED]>
Cc: <debian-devel@lists.debian.org>
Sent: Friday, October 22, 2004 1:56 AM
Subject: Re: an idea for next generation APT archive caching

Caching for concurrent clients is non trivial :). Theres not a lot squid
would need done, to make it an excellent archive-specific cache: