[MSITEMESH-28] Allow to use a custom cache key generator per fragment Created: 25/Feb/15  Updated: 10/Mar/15  Resolved: 27/Feb/15

Status: Closed
Project: SiteMesh
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0

Type: Improvement Priority: Neutral
Reporter: Roman Kovařík Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MGNLADVCACHE-44 Allow to use a custom cache key gener... 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:
Epic Link: DPC

 Comments   
Comment by Jan Haderka [ 25/Feb/15 ]

Not so happy about us adding some header as it could be in theory abused by someone knowing about what system does with it. Isn't there some other way to pass the info about which cache generator to use?

Comment by Jan Haderka [ 27/Feb/15 ]
  • I don't think that the token needs to be static when whole registry is singleton. or does it?
  • You should use AtomicLong for id instead of synchronised call around normal long.
Comment by Roman Kovařík [ 27/Feb/15 ]

https://git.magnolia-cms.com/gitweb/?p=enterprise/sitemesh.git;a=shortlog;h=refs/heads/MSITEMESH-28

Generated at Mon Feb 12 10:57:05 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.