Graham Leggett wrote:
A question to ponder is just how generic should the cache be. An HTTP
cache requires cache entries containing data and headers, either of
which can be updated separately.
So any given HTTP "object" would actually be two objects in the cache:
headers and data.
As a result, the typical "cache a blob
of data" interface isn't going to work, and needs to be kept in mind
when looking at the cache interfaces.
mod_http_cache could just cache headers and data as separate cache entries.
So a given HTTP "object" may actually have 3 entries in the cache:
-first entry says: Vary on x,y,z
-second entry is headers for new key (generated with the vary info)
-third entry is the actual data
As far as mod_cache is concerned these are 3 independent entries, but
mod_http_cache knows how to "stitch" them together.
mod_cache should *not* be HTTP specific in any way.
--
Brian Akins
Lead Systems Engineer
CNN Internet Technologies
