| Summary | Horde_Cache_Composite driver |
| Queue | Horde Framework Packages |
| Queue Version | HEAD |
| Type | Enhancement |
| State | Resolved |
| Priority | 1. Low |
| Owners | slusarz (at) horde (dot) org |
| Requester | chuck (at) horde (dot) org |
| Created | 06/30/2008 (6211 days ago) |
| Due | |
| Updated | 11/13/2013 (4249 days ago) |
| Assigned | |
| Resolved | 11/13/2013 (4249 days ago) |
| Milestone | |
| Patch | No |
Assigned to Michael Slusarz
State ⇒ Resolved
State ⇒ Accepted
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ Horde_Cache_Composite driver
Queue ⇒ Horde Framework Packages
Milestone ⇒
Patch ⇒ No
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