[MAGNOLIA-1273] CacheFilter Created: 14/Dec/06  Updated: 23/Jan/13  Resolved: 15/Dec/06

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 3.0.1
Fix Version/s: None

Type: Improvement Priority: Minor
Reporter: Stefan GrĂ¼nig Assignee: Sameer Charles
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Magnolia Cache


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   

I enabled the cache in magnoliaAuthor (I know i should not).

The current implementation does not consider the modification date of a node.
Why dont you check the cached data against the moddate of the contentnode ???

This would enable proper work of caching in any case.

OR

Enabling the cache in magnoliaAuthor wont start the cache itself.



 Comments   
Comment by Philipp Bracher [ 15/Dec/06 ]

Enabeling cache in the author environement should be possible (but as you pointed out correctly, it doesn't work with the current date check). The problem is, that the cache does not know how a page is rendered (cms filter, jsp, servlet, ...).

If you need caching on an author instance you have to exclude the most of the pathes or you have to enable observation to flush cache on changes.

Concludion: No way to implement it as you proposed, without introducing other problems.

Comment by Philipp Bracher [ 15/Dec/06 ]

If someone has a solution, I will reopen the task

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