If you need it and Xerces-C doesn't supply it... For Xalan-J, where we
can't assume that our input will always be coming from Xerces, we invented
a solution which involves two threads running in lockstep with each other.
One thread generates the SAX events, the other consumes them, and some
handshaking code (IncrementalSAXSource) deals with putting the source to
sleep, and waking it up for a few events only when the consumer requests
more data. Another implementation of the same API uses the "real"
incremental parsing support from Xerces-J, so the application can take
advantage of that when it's available.
It'd probably be possible to do something similar in the C++ world. Start
with multithreading and handshaking, but wrap it up in an API that lets you
switch to genuine parse-on-demand later without updating your code.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
