On Friday, Nov 22, 2002, at 15:21 Europe/London, Robin Berjon wrote:
No.no.no.no!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 :)
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]
