On Sat, 20 Sep 2003, Arne Claassen wrote: > I share the the writer's dislike for XPathScript, but I also dislike XSP, > JSP, ASP and PHP, or basically any technology where presentation of your > data contains the logic to produce the data. I don't see why he dislikes > XSL, and he gives no argument for his dislike. I think XSL is quite nice and > since most browsers can even render it themselves, a great tool to base your > architecture on.
I'm curious why you would lump XSP in with JSP, ASP and PHP. As long as your XSP is generating pure data-oriented XML from calling library functions, then it seems to me that it's quite free of presentation logic. I'm speaking from experience on this, too. We probably have 300-500 xsp/xsl pairs in our various sites' codebases, and none of our .xml files are static. Also, you can see it in action at sites like http://shop.newline.com/ . We're also using a dynamic pipeline like you describe for selecting which set of xsl files should be applied to the xml data (it's called the "pipeline", and is somewhat analogous to Cocoon's sitemap). > I am admittedly an abnormal user of AxKit, spending a lot of time trying to > get it to work in a way it wasn't quite set up for. But my end goal is > simple: Separate Data, Business Logic and Presentation completely. And to > that end AxKit's a very useful framework for me. Basically, i'm trying to > get AxKit to work like a internal, proprietary stylesheet system I used at > my last company and had to leave behind. Data is in XML only, presentation > is in XSL only. XML data is either static or generated by Business Logic, in > my case mod_perl. And finally, the application of stylesheets to XML is > based on a hierarchical search tree, i.e. look for an xsl of the same name > in the same directory, then fall back to the default for the directory, then > fall back up the directory tree, finally fall back to a site default. > > This way, my business logic never knows anything about presentation or what > site is being served the data doesn't care who uses it and stylesheets can > be customized to the client which will receive the data, which may or may > not be HTML. > > I just never want to see another bit of data with code in it, another > stylesheet with perl in it or another app with HTML in it. > > But i suppose it comes down to the programmer more than the tool, since it > seems people have been able to build quite maintainable systems with PHP, > JSP, ASP, etc. And conversely people have also been able to to produce utter > garbage. > > cheers, > arne > > ----- Original Message ----- > From: "Matt Sergeant" <[EMAIL PROTECTED]> > To: "AxKit Users" <[EMAIL PROTECTED]> > Sent: Saturday, September 20, 2003 3:08 AM > Subject: AxKit on Slashdot > > > > http://developers.slashdot.org/comments.pl?sid=79259&cid=7010580 > > > > :-) > > > > Matt. > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
