DOM vs. SAX??? Nah. (was RE: Storing Lots of Fiddly Bits (was Re: What is XML for?)

[Clark Evans]

Bill la Forge wrote:
> 
> The advantage of SAX is its independence from DOM,
> as that allows for the development of SAX components
> (filters) which can be used for
>     1. Preprocessing events before they are used to build the DOM;
>     2. DOM construction;
>     3. Output formatting from a DOM or without a DOM;
>     4. Simple document transformations.
> 
> What I'm more inclined to do in this SAX/DOM marriage,
> is to create an alternative to the SAX helper class, AttributeListImpl,
> which also implements
>       public Attr setAttribute(Attr newAttr);
> and
>       public Attr removeAttribute(String name);
> and
>       public Attr getAttribute(String name);
> 

This is a nice idea.  Factor out the common, helper 
objects used by both the document-oriented DOM and the 
event-oriented SAX.  This would be pretty.  It would allow
a marriage, but yet keep their independence (which is the
key to any successful marriage).

:) Clark

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/ and on CD-ROM/ISBN 981-02-3594-1
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)