[MAGNOLIA-1892] cache: decoupled cache flushing Created: 27/Nov/07  Updated: 23/Jan/13  Resolved: 27/Jun/08

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

Type: Improvement Priority: Major
Reporter: Philipp Bärfuss Assignee: Magnolia International
Resolution: Fixed 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   

We do flush the complete cache on activation. We should provide better strategies for that. A simple strategy could be:

  • mark cache as outdated
  • on request start recaching of the page/resource
  • until the page/resource is fully cached serve the old cached content

This would make sense for pages which need heavy computation or in installations in which you activate every now and then



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

cache flushing is now configurable/replaceable

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