SAX2: Namespace Processing and NSUtils helper class

Niels Möller nisse at
Thu Dec 16 16:09:51 GMT 1999

David Megginson <david at> writes:

> Every level of indirection is an open flame because it increases the
> difficulty (and cost) of learning and implementing an API, which
> leads to several problems:

In my experience, extra indirection should be safe and with no
surprises as long as there are no destructive mutations involved. If
you create the name instances (and appropriate hash and equality
methods that says that names are equal iff both of their parts are
equal), with both parts filled in when the object is instantiated, and
if you disallow all further destrucite changes, I think you should be
pretty safe.

If you do this, you could also use some kind of (weak) hash table from
strings "{ns}local" to name instances, in order to share name
instances where possible.

I'm no java expert, but in general I think it sounds very reasonable
to use some object oriented model for the particular
"name"-abstraction defined by XML and the namespaces spec.


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