Plüm wrote:
Agreed. If it turns out that the common code base between both cases is only small and it is complex to do both things in one provider just make two providers out of them. The remaining common code could be factored out in a separate disk_cache_util c file which is used by both providers.
It may be possible to even decide which provider to use based on various factors: object size (content-length), time of day, phase of moon, cpu usage, disk io, cache size etc. Could be as simple as shoving the provider in an env like "cache-provider = brians_wacky_memcache" and mod_cache tries that one first.
-- Brian Akins Chief Operations Engineer Turner Digital Media Technologies
