Davi Arnaut wrote:

mod_cache need not be HTTP specific, it only needs the ability to cache multiple entities (data, headers) under the same key, and be able to replace zero or more entities independently of the other entities (think updating headers without updating content).

mod_cache needs only to cache key/value pairs. The key/value format is up to
the mod_cache user.

It's a design flaw to create problems that have to be specially coded around, when you can avoid the problem entirely.

The cache needs to be generic, yes - but there is no need to stick to the "key/value" cliché of cache code, if a variation to this is going to make your life significantly easier.

Regards,
Graham
--

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to