[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: SAX2 RFD: Inheritance vs. Modification vs. Amalgamation

• From: Tim Bray <tbray@t...>
• To: David Megginson <david@m...>, "XML Developers' List" <xml-dev@i...>
• Date: Wed, 19 May 1999 09:25:50 -0700

At 11:20 AM 5/19/99 -0400, David Megginson wrote:
>2. Add the methods to org.xml.sax.Parser, and require applications to
>   catch NoSuchMethodException when using the new methods, in case
>   they're concerned about what version they're dealing with.
>
>   PRO: - doesn't limit options for subclassing in the future
>   CON: - very difficult to write adapters for existing SAX 1.0
>          drivers (slower acceptance and implementation of SAX2)
>        - can cause unexpected behaviour at deployment time, unless
>          the application designer knows to catch
>          NoSuchMethodException

Still, this seems the right thing to do.  SAX has been successful, but
of all its eventual users, 95% haven't started or even heard of it 
yet.  Face the legacy-code issue and deal with it and just make SAX
as good as possible for the long haul.  -Tim

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
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@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• Prev by Date: Re: SAX2 and XSLT processors
• Next by Date: Re: SAX2 RFD: Inheritance vs. Modification vs. Amalgamation
• Previous by thread: Re: SAX2 RFD: Inheritance vs. Modification vs. Amalgamation
• Next by thread: Re: SAX2 RFD: Inheritance vs. Modification vs. Amalgamation
• Index(es):
  • Date
  • Thread