Lists Home |
Date Index |
- From: "Bill la Forge" <firstname.lastname@example.org>
- To: "David Megginson" <email@example.com>, <firstname.lastname@example.org>
- Date: Mon, 8 Mar 1999 19:13:21 -0500
From: David Megginson <email@example.com>
>I expect the number of features to grow slowly
I suspect otherwise. Especially since the interface would also
be used by filters and DOMWlakers.
Think of the get and set methods as ways of accessing the
properties on filters which are part of some larger filter
structure (a stack being the simplest case).
In addition to parse events moving from parser-kernel to
application via a series of filters and event routers, the
get and set "events" move from the application through
the filters and down to the parser-kernel.
Think of the parser and the filters together as a large aggregate
of components. The get, set, setFeature, and setHandler
may well be intercepted by any component in that aggregate
which recognizes the featureID, handlerID, or infoID.
I see the ModParser interface as currently defined as being
very important for filters, with the number of featureIDs growing
with the popularity of such filiters.
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)