Currently the cache engines takes their configuration directly from $conf. This makes it difficult to create them programmatically.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | 365065-refactor-cache-construct.patch | 5.39 KB | damien tournoud |
Currently the cache engines takes their configuration directly from $conf. This makes it difficult to create them programmatically.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | 365065-refactor-cache-construct.patch | 5.39 KB | damien tournoud |
Comments
Comment #1
damien tournoud commentedHere is the patch.
Comment #2
david straussSubscribe.
Comment #3
andypostNice idea! One step to pluggable cache... per-user configurable storage
Comment #4
andypostSuppose every backed should have static method to provide info about own's config:
memcache - servers with params
file - folder
apc, eacc, xcache - none.. but maybe sometime
cacherouter.module already have admin section with statistics so another tab with options (settings) or per statistic-backend link to it's own settings
I will return to this latter with code but first better talk about that
Comment #5
slantview commentedApplied patch to 5/6/7 branches. Should make it easier to extend cache router to do dynamic cache creation. Should be interesting what comes from this.
Thanks a ton.