I have been performing thought experiments (in other words, I haven't
actually tried it out :-) on how to delay loading of external entities using
SAX. The scenario is you want to do browser style incremental presentation
where you delegate any external entity loading to separate SAX pipelines.
You want to spew the overrall structure into the users' face as quickly as
possible and then fill in the blanks.
My impression of the SAX architecture is that the parser is expecting to
handle all loading of external entities itself. It will call the
EntityResolver expecting to get either a system identifier or a stream.
There doesn't seem to be a third possibility of "ignore this entity".
It seems you can fake this by returning a dummy stream to the parser from
your resolver. This dummy stream would have minimal well formed content
(could it be empty?) and then on you go. Are there other possibilities?
Gabe Beged-Dov
www.jfinity.com
xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)