• From: "Don Park" <donpark@q...>
• To: <xml-dev@i...>
• Date: Wed, 2 Sep 1998 05:27:38 -0700

>I would suspect that the DOM package provided by Don Park has similiar
>performance and memory consumption.  Your best bet would probably be to
look at
>an XSL package which takes a DOM tree of your XML data, and a DOM tree of
an XSL
>stylesheet and spits out the content.  That way you are not stuck with an
MS,
>IBM, Oracle, or whatever implementation that you are not happy with.


About 10 seconds and 10 meg of memory to convert each meg of XML into DOM
with JIT enabled.

My solution to the problem of DOM building speed is based on that famous
doctor joke about a guy telling his doctor "Doctor, it hurts when I do
this!".  The trick lies in reducing the need to build DOM everytime the XML
document changes.  Unless you are into pain, that is.

Don



xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• Follow-Ups:
  • Re: XML tools and big documents (was: Re: Is there a size limitation on XML file given to MSXSL as input?)
    • From: Tyler Baker <tyler@i...>

• Prev by Date: Re: xsl query or transformation language
• Next by Date: Re: XML-QL
• Previous by thread: Re: XML tools and big documents (was: Re: Is there a size limitation on XML file given to MSXSL as input?)
• Next by thread: Re: XML tools and big documents (was: Re: Is there a size limitation on XML file given to MSXSL as input?)
• Index(es):
  • Date
  • Thread