J:
No offense meant, but most people start with the most
inefficient ways to generate XML, usually doing a
lookup in a remote database (which is slow, but hard to
avoid), building an XML string or a DOM tree (which is
slow, memory consuming and avoidable) and then feed it
to the XSLT
That's really good to know. Thanks
Matt Savino
Doesn't XSLT ultimately need it's source XML in a DOM
object to run?
It depends. One point is that DOM is an interface, and there
exist heavyweight and leightweight implementations. Some
XSLT processors can work directly from an arbitrary
Savino, Matt C wrote:
Doesn't XSLT ultimately need it's source XML in a DOM object to run?
Certainly not if you are talking about java processors. Moreover source
xml in DOM form often means wastefulness of memory and cpu since almost
every xslt processor always builds its own *optimized*
Zahigian, Mike wrote:
I am using FOP to take a single page of XSL:FO content and convert to PDF.
I have embedded FOP in a servlet. When I have one user requesting a page it
takes about 6 or 7 seconds to get the page formatted as PDF. It seems like
each additional simultaneous request pushes the
06, 2002 1:51 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Performance Guidance
I am curently working on a system to only allow one FOP processing thread
per appserver instance. You can search my earlier posts for some
benchmarking results.
Matt Savino
Senior Systems Analyst
Quest Diagnostics Inc
of the details.
Matt Savino
-Original Message-
From: Zahigian, Mike [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 06, 2002 2:13 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Performance Guidance
Matt, I'm not sure what you mean by a one FOP processing thread per
appserver instance?
J
I get it. Do you know if I can similarly limit the number of instances of a
servlet to one?
Mike Z.
-Original Message-
From: Savino, Matt C [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 06, 2002 2:17 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Performance Guidance
I mean every other
