On Tue, Aug 16, 2005 at 06:02:04PM -0700, Justin Erenkrantz wrote: > The quick handler runs well before any knowledge is available about the > backend (dir/file). The only thing you know is the URI path: unsurprisingly, > this is all that CacheEnable and CacheDisable can reasonably work with.
It's not the only thing, we also have the Cache provider itself. If that lookup is quick enough (it certainly would be for say mod_mem_cache) that's how you determine if it's cached. >From experience with mod_disk_cache, I don't it's hit as all that expensive either, I run millions of requests through "CacheEnable disk /" per day without problem, but I still have to concede it is going to be slower than a few strcmp's. By the time the cache_save_filter is run, the directory walks have happened, so deciding cachability there is trivial. > The only way to resolve this is to do the directory walks and file resolution; > but that is *very* expensive to do per request. -- justin My changes didn't need this at all. -- Colm MacCárthaigh Public Key: [EMAIL PROTECTED]
