[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: Kay Michael <Michael.Kay@i...>
• To: "XML Developers' List" <xml-dev@i...>
• Date: Wed, 19 May 1999 17:32:04 +0100

I'd go for an amalgam of (1) and (3): define a new interface Parser2 that is
forwards-compatible from Parser but *doesn't* extend it. Give the supplier
the choice of implementing either or both interfaces (in the same or
different classes). The user decides which interface he's going to use and
selects a product that supplies it.

This makes it difficult to write a client application that will work
directly with either interface, but the availability of adapters (in both
directions) should mean this isn't a problem. The fact that Parser2 doesn't
extend Parser will ensure that the old Parser interface eventually falls
into disuse.

Mike Kay

> 
> 1. Create a new interface, org.xml.sax.Parser2, that extends
>    org.xml.sax.Parser.
> 
> 3. Create a separate interface org.xml.sax.ParserProps (or something
>    like that), and require SAX2 drivers to implement both interfaces.
> 

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 RFD: Inheritance vs. Modification vs. Amalgamation
• 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