Putting XSP later in a pipeline is also horribly inefficient because the XSP
has to be compiled to perl for every single request. Normally a static XSP
page will be compiled to a perl module ONCE and the resulting perl script
cached, but if the XSP itself is dynamic then that cannot happen. You will
find that it can take a HUGE amount of excess processing when XSP is later in
the pipe. Even supposing you can get it to work reliably I do not thing it
will ever be a good idea to use XSP that way.
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 ;-)
Yes, you'd be asking us to solve the Halting problem. :-)
But now I've seen more of what you want to achieve I've realised that all you need is a plugin. And probably Apache::AxKit::Plugin::AddXSLParams::Request will do everything you need.
Matt.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
