I could be wrong, but from what I can see there should be few performance issues with having a processing chain with several stylesheets. The reasoning is thus:
Each stylesheet gets converted ONCE to a DOM tree. Thus if you had 3 or 4 smaller stylesheets vs one big one, you simply have several smaller DOM trees to process, vs one larger one. XSP uses the same underlying DOM API that XSLT uses, so doing things in XSP vs XSLT shouldn't really represent much difference in performance either. The document() XSLT function's performance however is an open issue, I don't know if there is any caching of what gets parsed by that, perhaps not. If that proves to be a problem you might use an XSLT Include instead, which since it parses into the stylesheet's DOM tree would only happen once. In that case you would engineer an XSLT template which contains the XML/XHTML for your navbar and can pull in some nodes from the main document for overriding or whatnot. The only extra overhead I can see in longer processing chains is the fact that the XSLT processor gets called more times from AxKit, so perhaps there is some startup cost there, but I expect that since everything is already loaded in memory it should be pretty minimal. It may even be that several smaller stylesheets are FASTER simply because each one is simpler to traverse. Daemmon and I haven't done much loadtesting on our application as of yet, but so far things seem to work pretty snappy for us. :o). On Wednesday 24 April 2002 10:18, Markus Jais wrote: > On Wednesday 24 April 2002 16:19, Daemmon wrote: > > On 24 Apr 2002, at 14:03, Markus Jais wrote: > > > when I transfrom it with xsltproc it works just fine. > > > but when I access it with my browser the content of the > > > "subnav.xml" and "topnav.xml" file are not inserted. > > > > > > but it is essential for my application that I can include xml files > > > in other xml files like this. > > > > Since you are using XSLT you can use the document() function in > > your login.xsl. > > > > One step better might be to create another stylesheet (say > > addnav.xsl) that uses the document() function to pull in the nav > > files. The you could then use it as a "library" stylesheet on any > > page in your site: > > > > <?xml version="1.0"?> > > <?xml-stylesheet href="." type="application/x-xsp"?> > > <?xml-stylesheet href="login.xsl" type="text/xsl"?> > > <?xml-stylesheet href="addnav.xsl" type="text/xsl"?> > > thanks for your tip. but I am not sure if using another stylesheet > might be too much of performance overhead, because it means building > more XSLT trees in memory and performance is very crucial to our > application, but I still want to use Axkit. > > maybe I have to make some tests > > markus > > > Daemmon Hughes > > > > --------------------------------------------------------------------- > > 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]
