Lists Home |
Date Index |
- From: John Cowan <firstname.lastname@example.org>
- To: XML Dev <email@example.com>
- Date: Mon, 08 Mar 1999 17:12:16 -0500
David Megginson wrote:
> Wouldn't it be better to allow the parser/filter make that decision?
> > 2) This method is allowed to throw a SAXNewParserException, which
> > encapsulates a replacement parser. The application should use
> > the parser inside the exception in place of the original parser.
> > This allows parsers to push filters on top of themselves, which
> > complements the ability of applications to push them.
> I think that this could be layered on top of SAX, simply by
> subclassing SAXNotSupportedException.
Yes, but by making it part of the core SAX protocol for setting
features, we guarantee universal support for it. A parser that knows
itself to be naive about namespaces can load the NamespaceFilter and
push it on top of itself, almost transparently to the application.
Otherwise, every application that wants namespace support needs
specialized knowledge about how to recover from SAXNotSupportedExn.
John Cowan http://www.ccil.org/~cowan firstname.lastname@example.org
You tollerday donsk? N. You tolkatiff scowegian? Nn.
You spigotty anglease? Nnn. You phonio saxo? Nnnn.
Clear all so! 'Tis a Jute.... (Finnegans Wake 16.5)
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)