Joe Orton wrote:
I think it's appropriate that the "smallness" is brought out:1) the fact that some providers (shmcb, memcache at least) have fixed size limits means any consumer must be designed to cope with that,2) for a cache which could store arbitrarily large objects, you'd want a different, streamy, interface, which didn't just pass data blobs as (char *, size) pairs.
One thing I see a definite use for a small object cache is in mod_disk_cache, to store the headers of requests. This will allow the update of headers without the song and dance that we have to go through now to do this.
Headers fit the criterion of "small" and "fixed size limits", but would need to be persisted across a server restart somehow, ie with DBM or DBD.
Regards, Graham --
smime.p7s
Description: S/MIME Cryptographic Signature
