>>However, it's worth pointing out that you may wind up wanting to make >>multiple implementations of the DOM available, tuned for different >>purposes. You may or may not want to consider that when picking your >>package name.
And that brings out another issue: we lack an abstract DOM in C++. The org.w3c.dom.Node, etc. Java classes are interfaces, so you can at least imagine having several tuned implementations. But the C++ dom\DOM_Node class is a non-abstract, non-polymorphic wrapper of NodeImpl. I think it would be grand if we had a set of abstract base classes for DOM_Node, etc. Would this cause an especially bad performance hit, adding a vtable to each node?
