Re: [OT] Re: Apache Module (Xalan?)

Subject: Re: [OT] Re: Apache Module (Xalan?)
From: "Khalid Asad" <asad@xxxxxxxxxxxxx>
Date: Thu, 1 Jun 2000 15:55:33 -0400

Thanks for your comments.

I have a lot of documents to transform against the same stylesheet, so I'm
hoping I can compile the stylesheet exactly once when the system starts up.
Right now I'm using Xalan, but I can consider others.


----- Original Message -----
From: "Jon Smirl" <jonsmirl@xxxxxxxxxxxx>
To: <xsl-list@xxxxxxxxxxxxxxxx>
Sent: Thursday, June 01, 2000 2:30 PM
Subject: Re: [OT] Re: Apache Module (Xalan?)

> I haven't measured it exactly since it was so slow but there is a big
> different between compiled and not compiled. The XML parser is about the
> same speed as the XSL transform stage. Compiling the sheet each time means
> you have to parse it each time which will half your throughput.
> My XML input to the compiled XSL sheet is never parsed either. My db
> integration code generates SAX events straight into XT allowing me to
> another XML parse. Retrieving a page from my system does not involve any
> parsing once the cache is active. For Java based systems XT/XP is twice
> speed of any of the other available solutions.
> Another trap is the document() function for making the stylesheet
> for input into the transform. XSL and XML don't treat white space the same
> so the DOM trees have to be different. Using document() will cause the XSL
> sheet to be reparsed.
> None of these schemes are fast enough for building an interactive
> app with fifty simultaneous users. It looks like C based code is my only
> solution. Now that MS is up to speed on the XSL bandwagon I'm looking at
> moving all of my transforms into the browser.
> Jon Smirl
> jonsmirl@xxxxxxxxxxxx
>  XSL-List info and archive:

 XSL-List info and archive:

Current Thread