It's a bit of a maintenance problem. I like the idea of AxKit looking after everything for me. The trouble with pre-processing the XML is that the people who are writing the XML pages don't necessarily want to do that. They would prefer to write documents and upload them, end of story.
-----Original Message----- From: Aidas Kasparas [mailto:[EMAIL PROTECTED]] Sent: 31 July 2002 09:15 To: Adam Griffiths Cc: [EMAIL PROTECTED] Subject: Re: Pipelines Adam Griffiths wrote: > I had two things on my mind: > > 1. I want the same Dynamic, XSP, code on many pages so and it would be > a maintenance problem to have to edit every page to make a change to > it. So I thought I could have a single tag, say <dynamiccontent/> on > each page that requires it and have an XSLT expand it to XSP tags then > the XSP processor process it. > > 2. The idea of outputting the PI <?xml-stylesheet href="NULL"> > type="application/x-xsp"?> only if necessary, was that if > <dynamiccontent/> exits then <?xml-stylesheet href="NULL"> > type="application/x-xsp"?> would be needed, otherwise not. > > I will have the XSP code generated by the 2nd stage of the pipeline > and it will be the same every time. Therefore I _would_ like AxKit to > cache the perl bytecode, for efficiency. However I understand that > AxKit might not know the 2nd stage results are going to be the > constant and therefore decide not to cache the bytecode. > > So my two questions are: > > Can I tell AxKit to cache the perl bytecode even if the xsp is not the > first stage of the pipeline? (but, naturally, re-generate it if any of > the dependant files change.) > > Is there a better way to achieve my aim? I guess I could write a > taglib but I like the idea of using xslt and the pipeline. > How about offloading xslt step to command line/cgi/etc tool which publishes your document to AxKit server? I mean: - in document you edit there is tag <dynamiccontents/>; - when you finished editing, you process this using xslt processor of your choice and put result to AxKit server; - depending on output of xslt processor xsp will or will not be executed by AxKit. This way you save on: - constant xslt processing for every request; - xsp will be first processor, so it will definitely work and cache perl code. Or is this too big maintenence problem? Aidas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
