I'd show you what I did, but it would take a few files to get down to the level of database...
Basically I look at XSP as just a macro language, and taglibs are perl macros. The taglibs themselves are just a thin layer of user interface abstraction on top of calls to application level APIs which contain all the logic for my webapps, with the exception of input validation, which I do in a seperate taglib for flexibility. This way I can write an old-fashioned CGI if I want and reuse 99% of the code. Anything you do with ESQL taglib and <xsp:logic/> is NOT portable, period! Not even portable to another page in your own site (and with webapps there is a lot of duplication, consider that for ever page that lets some user add something to the database with a form there will be an almost identical form to edit that data, and often its more like 3 or 4 forms). Actually I went one level further for larger apps, and I consider the entire user interface to be one tier and build the application as a 3-tier system with taglibs calling stubs that make SOAP calls to implementations in middleware that then interface with database via DBI. On Tuesday 19 November 2002 12:20 pm, Matt Sergeant wrote: > On Tue, 19 Nov 2002, Kjetil Kjernsmo wrote: > > Hi list! > > > > I'm a newborn axkitten who are seeking a new home after having worked > > with Cocoon for three months and given up... They're not paying too > > much attention to documentation over there, and the implementation > > seems rather fragile. Basically, what I went there for was a strict > > separation of logic from the rest, and a decoupling of site URLs from > > the underlying file system of the server machine. It took me a long > > time to realize that Axkit puts a lot more into their XSP than Cocoon > > does, that's pretty much the reason why it took me so long to come > > over... :-) > > > > Anyway, in Barrie's great tutorial on "XSP, Taglibs and Pipelines", he > > suggests that one should only use ESQL for small applications, and > > rather use DBI. I've googled around, but I haven't found anything that > > details this. So I wondered if you have any pointers for a little > > axkitten looking cutely at you from the basket...? :-) > > Basically the difference is that in AxKit (unlike Cocoon) it's absolutely > trivial to write a taglib. So it's better to hide your database access > behind a taglib if you can, rather than directly putting the SQL in your > XSP pages. > > There's a cool slide in [1] that details someone's XSP page that basically > hides an enormous amount of detail behind two tags. That's the idea. > > [1] http://axkit.org/docs/presentations/tpc2002/axkit.axp/axkit.pdf -- Tod G. Harter Giant Electronic Brain --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
