SAX2: Namespace proposal

[Stefan Haustein]

> For example, I think there are good arguments for moving to a
> 
> interface DocumentHandler {
>   void startElement(StartElementEvent event)
>   void endElement(EndElementEvent event)
>   ...
> }

I also would prefer this kind of interface. Further advantage besides
the improved extensability might be that 

- building a new object seems some overhead at the first sight, 
  but in JAVA also a new String is a new object...

- some computation could be performed on demand only(?) 

- I think it is less difficult to remember the access method names 
  than a more or less unmotivated order of a lot of parameters

- the ElementEvent access methods could be a subset of the DOM access
methods (!)

please do not forget to include the "old" SAX 1 methods in HandlerBase
and call them from the new methods as default behaviour preserving
compatibility at least with applications extending
HandlerBase instead of implementing DocumentHandler. 

All the best,

Stefan


-- 
KJAVA AWT project: www.trantor.de/kawt
SAX-based access to WBXML and WML: www.trantor.de/wbxml

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 unsubscribe, mailto:majordomo at ic.ac.uk the following message;
unsubscribe 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)