[ http://jira.magnolia.info/browse/MAGNOLIA-1273?page=comments#action_13061 ] Philipp Bracher commented on MAGNOLIA-1273: -------------------------------------------
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. > CacheFilter > ----------- > > Key: MAGNOLIA-1273 > URL: http://jira.magnolia.info/browse/MAGNOLIA-1273 > Project: Magnolia > Issue Type: Improvement > Components: core > Affects Versions: 3.0.1 > Environment: Magnolia Cache > Reporter: Stefan Grünig > Assigned To: Sameer Charles > Priority: Minor > > 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia.info/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
