mån 2006-05-22 klockan 23:17 -0300 skrev Gonzalo Arana:
Ah, I see now. As long as the helper squid follow lower level
number, higher priority policy, there is no need for cache
invalidation.
Correct.
To be able to make sane lookup structures it is very beneficial if the
data can be
Just to summ up:
Letting the helper do random combining/reordering leads into
highly-ineffitient lookup algorithm, and apparently it is not needed.
Cache level could structured in a 'path'-alike, or disjoint. Disjoint
solves reordering issue in an efficient manner.
Having each token a member
tis 2006-05-23 klockan 11:08 -0300 skrev Gonzalo Arana:
I would like to have a somehwat explicit cache level. Alternatives to this
is:
a) expand %| to some string: discarded.
b) helper tells squid about format specification cache levels upon startup.
c) squid notifies helper at startup
On 5/22/06, Henrik Nordstrom [EMAIL PROTECTED] wrote:
mån 2006-05-22 klockan 11:46 -0300 skrev Gonzalo Arana:
Reordering and combining perhaps? Allowing combining would raise the
number of cached entries invalidations from N-2 to (2**N)-2 (I am not
counting current reply as an
