Lists Home |
Date Index |
- From: "Bill la Forge" <email@example.com>
- To: "Oren Ben-Kiki" <firstname.lastname@example.org>, "XML List" <email@example.com>
- Date: Thu, 11 Mar 1999 07:42:28 -0500
From: Oren Ben-Kiki <firstname.lastname@example.org>
>I think you've hit on something important here. The Mod/X/Xtra/E-Sax thread
>has focused on "how to access extra functionality which is already available
>within a particular SAX parser implementation". This might be the wrong
>question to ask. Shouldn't it be "how to I obtain an instance of a SAX
>parser which provides the features I need", instead?
It is interesting how small shifts in perspective can have major design implications.
I just wanted to make it easy for new ModSAX applications to use older SAX
parsers without requiring any extra code in the application.
If ModSAX is to remain low-level, I suspect a registry is out of scope. As for building
up a parser with filters to meet a set of requirements automagically, I'd rather give
more control to the application to specify what it needs, than try to compose
something based on a feature list.
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)