| Summary | Horde_Cache_Composite driver |
| Queue | Horde Framework Packages |
| Queue Version | HEAD |
| Type | Enhancement |
| State | Accepted |
| Priority | 1. Low |
| Owners | |
| Requester | Chuck Hagenbuch <chuck (at) horde (dot) org> |
| Created | 06/30/2008 (143 days ago) |
| Due | |
| Updated | |
| Assigned | |
| Resolved | |
| Attachments | |
| Milestone | |
| Patch | No |
Patch ⇒
Milestone ⇒
Queue ⇒ Horde Framework Packages
Summary ⇒ Horde_Cache_Composite driver
Type ⇒ Enhancement
Priority ⇒ 1. Low
State ⇒ Accepted
generic version of the memcache layering that we have now - i.e.,
create a stack of request memory -> memcache -> disk or request memory
-> local disk -> database, that requests will cascade through.
It would also be great to have some sort of cache hints for calling
code to let the cache system know when things should never be cached
to memory (maybe a max size), etc. And stats on cache usage would be
good to have also.
http://schlitt.info/applications/blog/index.php?/archives/605-Hierarchical-caching.html