What would be so bad about using XSLT to generate perl. Then you can bring the full weight of XML processing technology to bear on the configuration of your pipelines, which can only be a good thing. Granted it might be a lot less efficient at compiling your XSP pages, but the fact is thats fairly irrelevant to performance since it only happens once. In a production environment you can always spider your site after you make changes in order to make sure everything is recompiled before you go live anyhow.
In terms of difficulty of management of the system, etc. Its always been my opinion that if you can reduce your system to the most common elements and processes, and then build good tools to do those tasks that in the long run you have the best system, so I'm not convinced that tools like SILLY are such bad ideas, they simply need to be presented as one set of possibilities. On Saturday 23 November 2002 09:41 am, Matt Sergeant wrote: > On Friday, Nov 22, 2002, at 15:21 Europe/London, Robin Berjon wrote: > > Tod Harter wrote: > >> It seems to me that XSP itself is an example of an application that > >> should be written in XSLT.... > > > > I've been going back and forth on that one, but after my last attempt > > (and failure) to patch XSP.pm I've become convinced that XSLT is the > > way to go. Starting from there we abandon the idea of ever switching > > XSP to SAX, and give the produced code full access to its own DOM :) > > No.no.no.no! > > This is a really bad idea. You end up with Cocoon. AxKit is fast and > light for a reason. XSP.pm isn't *that* hard to fix. Give me a test > case and I'll hack on it. This is the first bug reported in XSP.pm for > about a year, so there's not much to fix. > > Matt. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- Tod G. Harter Giant Electronic Brain --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
