Lists Home |
Date Index |
- From: "Bill la Forge" <email@example.com>
- To: "Lars Marius Garshol" <firstname.lastname@example.org>, "XML Developers' List" <email@example.com>
- Date: Thu, 25 Mar 1999 17:08:05 -0500
From: Lars Marius Garshol <firstname.lastname@example.org>
>| Frankly, I would love to see the design process for MDSAX2 as open
>| as SAX.
>Then let's start it here once SAX2 is out the door. For me, that
>means when I've released the Python version of SAX2. If SAX2 doesn't
>provide all I want with regard to filters I'll be very interested in
>working on a design that does, for implementation in Python.
After April would be best for me. Till then I'm pretty tied up.
I see almost all of the MDSAX interfaces being replaced by SAX2.
And I assure you, I plan to drop the current requirement of having
a setParser method from MDSAX2--a bad design decision on
my part is what caused it, and that created quite a few problems
Another problem was in the incompleteness of the AttributeList api.
Hard to make extensions to. And no way to add/update attributes
in a filter because of the incompleteness of the api. Typically you
check for the use of a known implementation and if it isn't being used,
replace the whole attribute list. And that really gets messy if you are
also trying to include extensions on the attributes!
One new problem for MDSAX being introduced by SAX2 is when
parser events are being routed between subfilters. These subfilters
may all need to be aware of application events, in contrast to a filter
stack where application events are handled by successive filters.
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)