On 2014-03-14 02:37, Omid Kosari wrote:
What about a learning mechanism . For example ObjectX is at urlA , urlB
,
urlC . It is no problem if squid downloads ObjectX from all of them for
ONE
time but after that it should delete it from cache storage and serve
all of
them from one file . And then squid should never download them again
until
they changed ( based on mechanisms which currently using to check that
an
object should redownload or not )
Also it would be more powerful if squid could learn some relation
between
urlA , urlB , urlC and if ObjectY requested from one of them , then
squid
GUESS the same behavior .
I know i am dreaming Utopia but discussion is better than silence about
it .
You just described how Store-ID feature works today.
The map of urlA == urlB == urlC is inside the helper. You can make it a
static list of regex patterns like the original Squid-2 helpers, a DB
text file of patterns like the bundled Squid-3 helper, or anything else
you like inside the helper.
Squid learns the mappings by asking the helper about each URL. There is
a helper response cache on these lookups same as other helpers and
prevent complex/slow mappings having much impact on hot objects.
Amos
