[MAGNOLIA-2616] Provide a method to flush page based on UUID and repository information from the cache Created: 11/Feb/09  Updated: 27/Nov/13  Resolved: 07/May/09

Status: Closed
Project: Magnolia
Component/s: cache
Affects Version/s: 4.0
Fix Version/s: 4.1

Type: New Feature Priority: Major
Reporter: Jan Haderka Assignee: Jan Haderka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MGNLCMNT-2 Flush page from the cache when adding... Closed
relation
is related to MAGNOLIA-2764 Cache module configuration may refer ... Closed
is related to MAGNOLIA-2756 Cleanup namespaces in some of our boo... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Comments   
Comment by Jan Haderka [ 11/Feb/09 ]

Done as of r22382.

Comment by Jan Haderka [ 11/Feb/09 ]

Fix only after 4.0 release.

Comment by Jan Haderka [ 16/Mar/09 ]

Done as of r23603.

Comment by Magnolia International [ 16/Mar/09 ]

This is not resolved until invoking code "guesses" the key instead of getting it from the appropriate cache policy instance.

Comment by Magnolia International [ 30/Apr/09 ]

I believe the fix version here is wrong since the latest changes were committed on the trunk

Comment by Jan Haderka [ 07/May/09 ]

The flush policies have been extended to allow for having multiple policies registered and to allow client code to hook in and ask cache to flush isolated change without having to know all the internal details of cache working.
Done as of r24820.

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