I understand all what you guys said, and my problem is that I saw my optimization problems thinking of pure OO conception ... I have to re-think it in more practical way !
Simon
Joseph Kesselman wrote:
ProcessingInstructionImpl inheriting from CharacterDataImpl pulls in some
methods that belong to CharacterData which aren't relevant to its
behaviour.
True, but since they aren't exposeed via the ProcessingInstruction interface, nobody outside the DOM implementation itself should be able to tell the difference.
Remember, there is no guarantee that the DOM node types are each implemented by a unique class... or that they don't implement other non-DOM interfaces as well. As an application programmer, you can't reliably use instanceOf or reflection to identify the node's type; you have to ask it for its type value.
Xalan, for example, includes a DOM proxy where all node types are implemented by a single class. That means a large number of the object's methods are invalid for any given node... but nobody should be calling them in those cases, so nobody should care. If you operate it via the DOM APIs, everything works.
______________________________________ Joe Kesselman, IBM Next-Generation Web Technologies: XML, XSL and more. "The world changed profoundly and unpredictably the day Tim Berners Lee got bitten by a radioactive spider." -- Rafe Culpin, in r.m.filk
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
