> > I am heavily using XML and XSL.
> >
> > Comment:
> > It is great. Using XSL I do not have to code conversion
> > code. Instead I need only write some rules and these will
> > generate the output. And I have a very good separation of
> > data from presentation. I can easily swap the XSL file to
> > create different presentations.
>
> I have experienced performance problems.
>
> /O
IMHO in terms of performance it does not really matter which
XSL engine you use.
I do the following to optimize performance:
+ I use a fast Java VM (Microsoft JVM)
With my old VM it took up to 8 seconds to create my HTML page.
With the new Java VM the page is created almost immediately.
+ I do caching
I load and parse the XML file only at the first access.
Additionally for property-file-like XML files I put the values
into a hashtable so I do not have to query the XML DOM again.
If the file modification date changes I discard the cached
entries.
For document-like XML files you can cache the resulting HTML
files in memory or on disk (or generate the HTML files
offline).
If you send plain XML/XSL to an XML capable client you should
not have performance problems, too.
Good Luck
Bernhard
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
