XML parsing memory overhead concerns

[James Clark]

"Clark C. Evans" wrote:

> Anyway, given a SAX event source, pushing
> the entire document his way, I don't see
> how a single threaded solution is possible.
> 
> And, from the expat declaration of setElementHandler,
> which requires both a StartElementHandler and an
> EndElementHandler, I assumed that expat works in
> a similar (if not identical) manner.

Expat doesn't work like SAX.  Clark Cooper has written a nice article
explaining expat's API:

  http://www.xml.com/pub/1999/09/expat/index.html

With SAX, the application calls parse once per document; the parser
makes a call on an InputStream to get each chunk of input.  With expat,
the parser doesn't make any calls to get input; rather the application
calls XML_Parse() arbitrarily many times for a single document, each
time passing it another chunk of the input.

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)