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

Re: ModSAX (SAX 1.1) Proposal

• From: "Don Park" <donpark@q...>
• To: "XML Developers' List" <xml-dev@i...>
• Date: Wed, 17 Feb 1999 14:43:04 -0800

David,

>What exactly do you mean by a "module"?


A feature by a different name and from the feature provider point of view.
I could have just as well used "Feature" instead of "Module".  I just
assumed that the "Mod" in "ModAX" was for "Module".

>In general, we don't have get* methods for org.xml.sax.Parser -- is
>there a special reason that we need one here?


It is just my style, ying and yang sort of thing.  I did not see any
compelling reason not to have it and there are some benefits such as chain
(as in chain of responsibilities) management.

>It certainly looks cleaner than checking a lot of boolean return
>values, and it provides stronger compile-time checking as well.


True if the feature in question is mandatory.  Code ends up a little messier
if the feature is optional.  If I just wanted to install different handler
types depending on whether a feature is available or not, we end up with
many try-catch islands.

Anyway, I like your latest proposal.

Best,

Don Park
Docuverse



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: from a new member
• Next by Date: Immediate opening for XSL Pro!
• Previous by thread: RE: ModSAX (SAX 1.1) Proposal
• Next by thread: Re: ModSAX (SAX 1.1) Proposal
• Index(es):
  • Date
  • Thread