Switching between DOM and SAX

[John Cowan]

Jonathan Robie scripsit:

> Lazy evaluation is perfectly OK in the DOM, which says absolutely nothing
> about the physical representation of a Node, e.g. it does not say that a
> Node must have a pointer, merely that it be able to return a reference to
> the root. Every Node must be capable of returning such a pointer when
> asked, but until someone asks for the root node, there is no need to
> construct such a node. Similarly, a Node must be able to return references
> to parent or child nodes, but those nodes need not be constructed until the
> reference is asked for.

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.

-- 
John Cowan					cowan at ccil.org
		e'osai ko sarji la lojban.

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)