SAX2/Java: Towards a final form

David Megginson david at
Mon Jan 10 18:59:32 GMT 2000

Stefan Haustein writes:
 > >  > Is "no namespace" reported with a null or empty String (for
 > >  > interned Strings, the equals problem does not exist)?
 > > 
 > > Empty string sounds like a reasonable suggestion when Namespace
 > > processing is being performed; null when it is not (so that a bugs in
 > > code will show up sooner).
 > To me, attrs.getValue ("", "href") looks strange, I would prefer 
 > attrs.getValue (null, "href"). But I could also live with the empty
 > string.  
 > I would not like if it is switchable, left to the parser, or both
 > allowed.
 > >  > Can I assume that namespace URIs are always interned?
 > > 
 > > That's a good question -- should SAX2 require that all names and
 > > Namespace URIs be interned (i.e. == to the results of
 > > java.lang.String.intern)?
 > I would suggest that only namespace interning is required: 
 > namespace URIs will be a small set of long strings, and
 > you do not meet them often while parsing. 
 > I think interning all names would slow down parsing too much (?). 

Or at least it would require some clever implementations.  Nearly all
parsers intern names anyway, but most use their own interning schemes
to speed things up.  To be compatible, they would need to call
java.lang.String.intern only once for each unique name (when it is
first inserted into the parser's private intern table).

I don't know if there's a lot of benefit in requiring this, though --
it's just a trial balloon right now.

All the best,


David Megginson                 david at

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at
Archived as: and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:majordomo at the following message;
unsubscribe xml-dev
To subscribe to the digests, mailto:majordomo at the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at

More information about the Xml-dev mailing list