cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <cziege...@sundn.de>
Subject AW: CachingCIncludeTransformer
Date Thu, 05 Jul 2001 13:10:55 GMT
Ahh, now I understand the trick! You assume (correctly) that
the underlying xml document used by the generator has not
changed, so you could use the old values of the validity
object. Ok, this should work.

Sorry for being so blind.

Carsten

> -----Ursprungliche Nachricht-----
> Von: maciejka@tiger.com.pl [mailto:maciejka@tiger.com.pl]
> Gesendet: Donnerstag, 5. Juli 2001 14:52
> An: cocoon-dev@xml.apache.org
> Betreff: Re: AW: CachingCIncludeTransformer
> 
> 
> On 5 Jul 2001, at 14:17, Carsten Ziegeler wrote:
> 
> > Hi,
> > 
> > are you sure that the CachingCIncludeTransformer is really working?
> > As far as I see the validity object gets all its information when
> > the first response is generated (the timestamps are added).
> > This hack works.
> > 
> > But when the second response comes in, the new validity object
> > for this response is empty. It is compared with the one from the
> > first run and they are not equal.
> 
> New validity object is not compared with the old one. Old one 
> contain two lists:
> source urls and timestamps. When it comes to checking validity of first 
> response we know that generation/transformation steps before 
> CIncludeTransformer are valid (otherwise we would have had 
> discarded cached 
> pipeline already) so source url list of new validity will be the 
> same as of old 
> one. Only timestamps have to be recalculated and compared. 
> 
> > The second validity object gets the timestamps after the
> > response is generated (or during the generation).
> > 
> > So as far as I understood your algorithm, I should cache the
> > correct result due to the hack but this is never retrieved from
> > the cache.
> > 
> > Or did I oversee something?
> > 
> 
> 
> Maciek Kaminski
> maciejka@tiger.com.pl
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message