Matthias Carlsson <[EMAIL PROTECTED]> wrote:

> I'm currently writing a web application where I'm generating a DOM-
> object in memory and then transforming it to HTML with XSL. This works fine,
> but the time it takes to finish a request is not acceptable.
>
> Currently (Tomcat 3.2.x) it looks like something like this
>
>       Generate the DOM-object for a page : 50-70 ms (acceptable)
>       Transforming DOM-object : 300-600 ms (not acceptable)
>
> Are these numbers "normal", or am I doing something terrible wrong
> somewhere?
> I'm using Xerces and Xalan from Apache.
>
> But, do get back on topic, I heard some time ago that some modern browsers
> (IE 5.5, Mozilla 6) handle client-side XSL-transformations. I assume this
> is done by sending both the XSL-document and the DOM-strukture to the
> browser and letting that take of everything (which would save server time).
> I'd like to be able to detect a browser which supports this so the server
> won't have to perform the transformation when the client can do it instead.
>
> Does anyone have information on this?

Those numbers seem AWFULLY wrong... The parse time is right, but the
transformation... NAAAAH... Can you check out using the JAXP-1.1 package
from Sun (including the Apache CRIMSON parser and the Apache XALAN XSL
transformer version 2.0)... Those should significantly reduce the time...

    Pier

--
----------------------------------------------------------------------------
Pier Fumagalli - Sun Microsystems Inc. - <mailto:[EMAIL PROTECTED]>

___________________________________________________________________________
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

Reply via email to