[MAGNOLIA-1534] CacheManager should rely on AggregationState rather than HttpServletRequest Created: 15/May/07  Updated: 23/Jan/13  Resolved: 10/Jul/08

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

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

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)

 Description   

This is just a rough idea, but it seems CM would be more flexible if it didnt depend on HSR; it could potentially be more easily used in other contexts (remoting...)



 Comments   
Comment by Magnolia International [ 09/Jun/08 ]

this is probably outdated for 3.6, we'll check.

Comment by Magnolia International [ 10/Jul/08 ]

yup - this is gone with MAGNOLIA-2127. The only dependencies on HttpServletRequest/Response are now in the filter and the executors, which are just the pluggable bits of logic extracted from the filter.

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