Am Wednesday, 23. July 2003 12:23, schrieb Adam Griffiths: > Hi, > > I've been using AxKit for a while now and I'd really appreciate any ideas > or information on the following question. > > XSP is great for generating dynamic XML documents and it's fast too. It > also caches the Perl code necessary to generate the dynamic XML page so > multiple requests only require it is parsed once. However as my application > grows and has an increasing number of XSP pages I am finding that many > share identical code / xsp-xml fragments, which makes maintaining them all > is becoming increasingly difficult.
Use taglibs or XInclude. If you find yourself reusing similar functional components, make a taglib of them. If you find yourself reusing data components, or lots of data with a little bit of logic, use XInclude. If you find yourself reusing a lot of data, try rearranging things so you do XSLT _after_ XSP. Of course, this combination does not work with logic inside your data. I use XSLT->XSP->... a lot, but as you already recognized, it's darn slow. For the caching behaviour you suggest you will have to wait for AxKit 2.0. It will most probably have that flexibility. -- CU Joerg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
