-
Improvement
-
Resolution: Fixed
-
Major
-
None
-
-
Empty show more show less
-
Yes
The current cache module is very biased towards caching pages (or request/responses in general).
We've already abused it to cache uuid mappings, and it'd be beneficial to do this for other things too (personalization could use it, forum, ...)
With our current API, one can get an arbitrary cache object by name, but that comes with FlushStrategy, etc, which are very likely irrelevant. Besides this unnecessary API leak, it is currently impossible to configurable such an arbitrary cache's underlying cache (i.e, for example, use different sizes and eviction mechanisms) - we can currently only configure the "defaultCacheFactory".
http://wiki.magnolia-cms.com/display/DEV/Concept+-+Cache+arbitrary+objects
- depends upon
-
MAGNOLIA-5263 Allow specifying transformer via @TransformedBy on class or annotation
- Closed
- is causing
-
MGNLCAT-138 Update cache-related update tasks to reflect new configuration
- Closed
-
MGNLSTK-1421 Update cache-related update tasks to reflect new configuration
- Closed
- is depended upon by
-
MGNLCACHE-78 Move store caching configuration into cachePolicy
- Closed
- is related to
-
MGNLCACHE-72 Update cache-related update tasks to reflect new configuration
- Closed
-
MGNLCACHE-32 Upgrade Ehcache to the latest (2.10.0)
- Closed
-
MGNLCACHE-75 Make it possible to share default configuration between multiple caches
- Closed
- relates to
-
MGNLCACHE-66 Explicitly prevent an Ehcache named "default"
- Closed