cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <cziege...@s-und-n.de>
Subject RE: [IMP] Performance problems with TraxTransformer
Date Wed, 29 Oct 2003 09:05:08 GMT
Stefan Seifert wrote:
> Wouldn't it be better to extend the validity mechanism?
> When the master xslt does not change, the includes does not change either.
> It should be possible to use an extended validity object that,
> when parsing the xslt for imports/includes is finished, stores
> the modification date of the main xslt *and* the modification
> dates of all (recursivly) found depended XSLT pages as well.
> The validity check would have to check a couple of modification
> dates, but it is not needed to parse any XSLT again if it is not changed.
>
> I planned the implementation of such a mechanisme some time ago,
> but due to the lack of time i did not got very far. I hope to
> find the time in the next days/weeks, but i cannot promise
> anthing right now, unfortunately.
>
Yes, that mechanism would work also and might be a little bit better
from the user perspective. But of course, it makes the whole thing
more complicated.

Carsten


Mime
View raw message