RE: Java and XML

["Fernandez, Obed" <ObedF@mediaocean.com>]

Be very wary of XSL transformations in the browser. I was involved in a
six-month effort to get that approach working in a production environment.
We had lots of performance issues and unreliable results from the browser,
crashes, etc. Even on a relatively fast PC, large transforms tend to peg the
CPU and lock your browser screen beyond acceptable limits. We also had
extreme difficulties debugging browser-based XSL code, which needs extensive
Javascript usage. The Microsoft XSL engine is not fully compliant and is
missing certain vital transforms. XML is bulky. Some of our screens were
regularly downloading 500k or more of XML data -- not a good idea for
Internet apps.

In the end we ditched it and went back to JSP.

My 2 cents,
Obie Fernandez

-----Original Message-----
From: Jim Michael [mailto:jmichael@anytransactions.com]
Sent: Tuesday, February 19, 2002 12:09 PM
To: ajug-members@www.ajug.org
Subject: RE: Java and XML





> In that context, then, the web server is doing the processing 
> of the document using a conversion. 

Not necessarily, since some browsers (IE 6 for one) can do the XSLT
transformation, allowing you to offload that part of the work to the client.