events vs callbacks (was Re: SAX2 (was Re: DOM vs. SAX??? Nah. ))

Paul Rabin rabin at
Thu Feb 25 17:09:47 GMT 1999

At 08:05 AM 2/25/99 -0800, Gabe Beged-Dov wrote:

>There is alot of discussion of data models vs API. I would like to see
>control flow added to the axes that people argue about :-).

Yes.  In particular, the current model does not support having a single
application (or filter) handle input streams from multiple concurrent
parsers (or filters), since the parser owns the thread of control until the
parse completes.

Rather than changing the callback model, we could implement a compromise

 - parseInit() // initialize the parse state

 - nextParseEvent() // cause the next event to be delivered via callback

All of the multi-threading logic could be hidden in a layer on top of
existing parsers.

	- Paul Rabin

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

More information about the Xml-dev mailing list