On Tuesday 18 March 2003 02:45 am, Chris Leishman wrote: > > I don't know how AxKit tracks dependancies - but I would have thought > it possible to derive that if the original .xml hadn't changed and the > .xsl hadn't changed, then the output of that translation (the XSP page) > hadn't changed and therefore it wouldn't need to be re-compiled. But > perhaps I'm asking too much ;-) > Well, AxKit caching doesn't work that way actually. It caches the final output only. Yes of course if the input to the pipeline hasn't changed then the final output will be generated. My point was that if that output HAS changed then not only does your XSP page have to be RUN again, but because the XSP page itself was created during the transformation, and AxKit doesn't hold onto intermediate steps (though in this case it wouldn't matter, would it) then the XSP also has be be RECOMPILED INTO PERL AGAIN, which is a much more expensive proposition than just running it.
> Regards, > Chris -- Tod Harter Giant Electronic Brain --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
