ModSAX (SAX 1.1) Proposal

[Don Park]

>The ModHandler class seems particularily useless.  It just creates a
>completely unnecessary dependency between handler classes and the SAX
>package.  You could use Object just as well.


Two reasons:

1. Using java.lang.Object will make ModSAX Java-dependent.
2. Using ModHandler interface adds some compile-time type-check.

Only penalty is increasing the number of interfaces a class implements which
does affect the performance during runtime.  Very little penalty in most
cases.

<java_tip>
Most Java VM implementations search the interface list back to front so that
most often used interface (i.e. org.w3c.dom.Node) should be the last
interface in the 'implements' list.
</java_tip>

Best,

Don Park
Docuverse



xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)