SAX2: Namespace proposal

[Stefan Haustein]

> > - building a new object seems some overhead at the first sight,
> >   but in JAVA also a new String is a new object...
> 
> And that is why most parsers internalize strings rather than creating
> new ones, and that's why the SAX characters() and
> ignorableWhiteSpace() methods use character arrays rather than
> strings.  XML parsing shows up a lot of problems that Java programmers
> aren't used to, because it generates so many events (often tens of
> thousands) in only a few seconds.

OK, what about

 void startElement(String localName, AttributeList attr,
NameSpaceContext nsc)

NameSpaceContext could be unmutable and thus be reused while unchanged.
I could still remember all parameters since there is only one more at
the end :-) 

The parser would only need to check if the NSC has changed and could
reuse the same object otherwise. 

Best regards

Stefan

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)