Answered on the Xalan list; I think I forgot to hit reply-to-all so it may not get here. Brief summary:
1) There's nothing wrong with having both an implemention directly in the Xerces DOM, optimized for that DOM, and a generic-but-possibly-less-efficient version provided via Xalan. 2) Some form of mutation notification is necessary internally. How that's achieved is implementation dependent. The portable solution for the generic version is DOM Mutation Events. Internally, other options may exist; see how we implemented liveness of deep nodelists, for example. (In my other note, I said named node maps; chalk that up to lack of caffeine.) ______________________________________ Joe Kesselman / IBM Research --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
