[MAGNOLIA-1704] CacheKey should be calculated by CacheFilter instead of CacheManager Created: 27/Aug/07  Updated: 23/Jan/13  Resolved: 14/May/08

Status: Closed
Project: Magnolia
Component/s: cache
Affects Version/s: 3.1 M3
Fix Version/s: 3.6

Type: Improvement Priority: Major
Reporter: Sameer Charles Assignee: Magnolia International
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-2127 New Cache features and api Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

It will be much cleaner if we delegate the responsibility of creating cache key to the cache filter, Cache manager (strategy)
can only be configured on server level which makes it impossible to use different caching strategy for sub filter chains.



 Comments   
Comment by Magnolia International [ 08/Nov/07 ]

Cache key is now a String (since r12194) - can we get a status / progress on this ?
(since code has been committed already)

Comment by Magnolia International [ 16/Nov/07 ]

CacheFilter currently has a getCacheKey() method which can be overridden by subclasses.
(multiple cache filters in the same chain need different cache key generation mechanisms)

Comment by Magnolia International [ 14/May/08 ]

the cache key is now provided by the CacheStrategy - which is replaceable.

Generated at Mon Feb 12 03:29:31 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.