XML parsing memory overhead concerns (fwd)

[James Clark]

Paul Miller wrote:

> I read through Clark's writeup and I'm willing to give it another go. I
> think the main problem will be handling the reentrancy caused by the
> parser parsing a startElement, calling a handler in my interface, which
> calls back into the parser to get some element data, which causes
> another call to the parser to read more data, which causes the
> characterData handler to be called, which fills in the buffer passed by
> my code, and have it all unwind correctly. Perhaps this would be easier
> to think about if I had a few beers first...

In the scheme I described, the expat handlers simply append events to a
queue, so you have no reentrancy problems.

> Another issue is expat's license. I'm not very familiar with the Mozilla
> license, but presumably anything I build on top would also require the
> Mozilla (or GPL) license.

No.  The Mozilla license isn't like that.

> I personally feel the GPL license is too
> restrictive. Does Mozilla let code be used in commercial products where
> source code is not made available?

Yes. That's the main point of the Mozilla license.  It's requirements
are not at all onerous.

James



xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:majordomo at ic.ac.uk the following message;
unsubscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)