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 .
-- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Automatic-StoreID-tp4665140p4665174.html Sent from the Squid - Users mailing list archive at Nabble.com.Received on Thu Mar 13 2014 - 13:38:26 MDT
This archive was generated by hypermail 2.2.0 : Fri Mar 14 2014 - 12:00:04 MDT