Lists Home |
Date Index |
- From: David Megginson <email@example.com>
- To: XMLDev list <firstname.lastname@example.org>
- Date: Tue, 18 Jan 2000 09:26:45 -0500 (EST)
We've talked in the past about supplying better DOM support in SAX2
through features and properties. There are two options:
Define a read-only 'dom-iterator' feature that tells whether the
current reader is iterating over a DOM tree or not. Define a
read-only 'dom-node' property (valid only during parsing) that
returns the current DOM node.
The DOM iterator could either get the root DOM node through its
constructor (as I imagined), through a magic URI argument to
parse(), or as David B. suggested, by making the 'dom-node'
property writable outside of the parse.
Define the 'dom-iterator' feature, and possibly also a 'dom-node'
property for setting the initial node, but add a 'dom-handler'
property for an extension handler to report the current DOM node:
public interface DOMHandler
startNode (Node node) throws SAXException;
endNode (Node node) throws SAXException;
This saves a lot of unnecessary hashtable lookups.
Which of the two do people prefer?
All the best,
David Megginson email@example.com
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ or CD-ROM/ISBN 981-02-3594-1
Please note: New list subscriptions now closed in preparation for transfer to OASIS.