Re serialization in sub-project: Is the serializer going to continue to
support other implementations of the DOM in addition to our own?

If so, it may make some sense for it to be a separate sub-project under
Xerces' control and referenced/invoked by Xerces. If not, I agree there's
no reason to break it out.

Another alternative might be a generic serializer as a separate project and
a Xerces-specific built in, but then there's some code duplication in
applications which may be using their own custom DOM as well as Xerces'.



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to