Re: XML/XSL on the client for dynamic UI

> I've measured a total of about 1 second (on the server) to a) read the XML
> doc and parse it, b) read the XSL doc and parse it, c) transform the XML
to
> generate the HTML output. Every page is unique and thus the output or the
> XML input cannot be cached.  Sometimes, the XSL can be cached as it may
> contain common rules for many of the pages. This can reduce the total time
> by about 40%, still requiring over 500ms for each page based on the same
> rules.

On my system, I am in development mode, so I do not cache anything yet.  My
web application is all server-side XML/XSLT returning HTML to the client.  I
am using NT 4.0, JDK1.2.2, JSDK 2.0, JServ 1.1b3, Saxon 4.7, and Apache
1.3.9.  To load the XML, parse it, load the XSL, parse it, transform it to
HTML and return the results averages 200 ms.  The max request time was 365
ms.  This was at a request load of 10 req/sec.

I think that with caching, at least on the XSL Side, I could see that easily
drop in to the 50ms range.

I think that is very good.

Scott Sanders



 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list