Cart
[Home] [By Thread] [By Date] [Recent Entries]
From: Oren Ben-Kiki <oren@c...> >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. Bill 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...)
|
