Switching between DOM and SAX

Don Park donpark at quake.net
Sun Sep 20 21:51:37 BST 1998

>Sure, but in SAX (event stream) to DOM conversion, you need to capture
>*all* the SAX events if you are to be able to satisfy the guarantees
>that the DOM model makes.  You can't just decided to start DOMifying
>at some random element, because by then you have forgotten what the
>parent element is.  You either have to reify the SAX events and store
>them as such, or else create the DOM Nodes on the fly whether the
>user claims to want them or not.

Right.  Lazy evaluation is not possible when building DOM using SAX.


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

More information about the Xml-dev mailing list