.. the difference with 3.0 is that it's now based on observation
instead of hardcoded flushing from the activation receiver.
-g
On Mar 25, 2008, at 12:26 , Jan Haderka wrote:
Hi Tom,
indeed the entire cache is flushed on page activation by default.
As for the call you cant't track down, here's the hierarchy:
DefaultCacheManager.handleChangeEvents()
BaseCacheManager.flushAll()
DefaultCacheManager.doFlushAll()
CacheImpl.flush();
HTH,
Jan
On Mon, 2008-03-24 at 14:08 -0600, Tom Jensen wrote:
It looks like, according to i.m.c.cache.simple.CacheImpl on line 100
(ver. 3.5.x) that the Simple Cache implementation should flush out
the
entire cache every time a change is published out to the public
instance. I looked through that class and can't see anywhere that
the
flush() method is ever called on itself.
In doing testing only the page that is added/changed/deleted is
updated in the cache so there is a stale cache problem (take for
example a menu that is dynamically generated for each page, no other
page was removed from the cache so if the page was deleted/moved all
other pages would still show a link to that deleted/moved page).
Am I misunderstanding how the Simple Cache should work and I just
need
to implement my own caching to be more aggressive about clearing the
cache or should I expect it to flush the cache every time a change is
made to a page and published?
Thanks,
Tom
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
