[XML-SIG] minidom changes & additional modules

Martin v. Loewis martin@v.loewis.de
15 Feb 2002 10:13:22 +0100

"Fred L. Drake, Jr." <fdrake@acm.org> writes:

> I'd like to check this into the PyXML tree soon so that we can shake
> out any problems and maybe squeeze out more performance before
> integrating the changes into the standard library.

Please do; this all sounds very reasonable. I think the most
controversial one is

> Building a minidom DOM builder directly on top of pyexpat allows us to
> avoid about a third of the overhead, and such an implementation can be
> based on some code I wrote for the "Parsed XML" product for Zope.
> While the code was originally targeted to a DOM written for that
> project, most of it is adapting the pyexpat callback parameters to the
> DOM structures; modifying it to work with minidom has proved fairly
> easy.

The issue here is that there are atleast three competing such
implementations: xml.dom.ext.reader.PyExpat.Reader,
Ft.Xml.pDomlette.PyExpatReader, and your ParsedXML reader, so the
question is which one to use.

At IPC10, I've toyed already with integrating the ext.reader into
minidom, but I'm happy to throw that away.

Mike Olson is interested in dumping pDomlette in favour of minidom,
but that would require that there is a pDomlette compatible reader.
We could probably still use the API and implementation you've been
designing (especially since it appears to follow DOM Level 3); hoping
that we can provide the 4Suite-style reader API on top of that.

The one feature that Mike wants to see in the reader is optional
XInclude support; it should be possible to incorporate that from
4Suite once you have committed your changes.