On 2 Feb 2005, at 16:55, Dave Roe wrote:
In my mind, it is not a matter of whether the Perl code behind the taglib needs to be re-compiled, as it's not changing. It is more a matter of how to structure the pipeline so that the XML can undergo multiple XML transforms via taglibs.
The problem is that the no-caching of XSP is slightly hard coded. There are some features in there for specifying has_changed(), but nobody has yet used them to any effect (if you succeed then let us know!).
So even if you could pass the output to XSP again, the internals of axkit would try and run the first XSP every time, causing you really bad slowdown.
There may also be a problem with the namespace XSP gets compiled into - I think I bound it to just the filename (assuming that there would be just one XSP run per file) rather than to the filename and the position in the pipeline...
If it sounds like you're going to need to go digging into the internals it's because you are :-)
Matt.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
