[EMAIL PROTECTED] wrote: > My initial reaction is the proxy directory. It is a separate module, but > it only makes a lot of sense with the proxy.
I've done it so that it is completely independant of the proxy.
The idea is that the cache will be capable of caching any kind of
content, from proxy content to CGI content to PHP content to static
content - whatever.
The cache supports (or will support) various dynamic backends, such as
cache-to-disk, cache-to-memory, or cache-to-shared-memory. The user
configuration will determine which dynamic backend is in force for which
URL prefix. It will also be possible to have more than one dynamic
backend on an URL prefix - so that for example if a cache-to-memory
cache gets full, the data will spill over into the cache-to-disk cache.
Currently the main framework for everything is in place, I just need to
create some skeletons for the backend modules. Been doing other things
and haven't had a chance to finish this, but I'll get this sorted by the
end of the week so at least there is a proof-of-concept out there.
Regards,
Graham
--
-----------------------------------------
[EMAIL PROTECTED] "There's a moon
over Bourbon Street
tonight..."
smime.p7s
Description: S/MIME Cryptographic Signature
