cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Geoff Howard <>
Subject Private Cache in XMLFileModule (was Re: DO NOT REPLY [Bug 32095] - Cache Event invalidation not working with non sitemap components)
Date Mon, 08 Nov 2004 13:27:36 GMT
Can anyone knowledgeable about either the XMLFileModule or
non-standard uses of the Cache shed light on this bug or the issues I
address below?


On 8 Nov 2004 03:14:51 -0000, <> wrote:
> Cache Event invalidation not working with non sitemap components
> ------- Additional Comments From  2004-11-08 03:14 -------
> This is certainly a convoluted situation, but I think the problem is obvious:
> the XMLFileModule uses it's own private cache, and does its own private
> validity computations.  I guess this was necessary because the Cache is built
> around cacheable pipeline results, and the XMLFileModule does not usually act
> on pipelines (except in the case of the cocoon: protocol).
> So, the full solution would be to change XMLFileModule to use the Cache.  This
> may not be possible/desirable.
> I don't know if a work around is possible by changing the behavior of
> EventValidity.isValid().  The point of the event validity is that the source
> itself does not know whether it is still valid.  If it turns out that the Map
> the XMLFileModule uses for its validity is the same object that the event
> registry has access to, it may be possible to modify the behavior there, but
> it's not immediately clear to me if this will work.
> Geoff

View raw message