Streaming XML and SAX

[Bill la Forge]

From: Didier PH Martin <martind at netfolder.com>
>This architecture brings more work than required. An other way to do it
>would be (in fact we are already doing that with our DSSSL,XSL
>interpreters).
>
>a) parse the document or the stream
>b) a interpreter router check for certain Gi or Pi. On matching one, load
>the appropriate interpreter
>c) the interpreter interprets parsed GIs until the end of the document (in
>your example: </purchase>)
>d) When the end of the document is reached, the router goes back to listen
>mode for this multiplexed channel (a channel is a multiplexed stream within
>a session) and the interpreter is unloaded


It seems like something is backwards here!

If an application is processing a series of documents, once it has a universal 
type name for that document (root element name + namespace), it knows how it
wants to process the document and doesn't need a Pi. (What's a Gi? Is that XML?)

Also, you should be able to use the same parser for all document types and then do
the routing on the parse events, saving you from having to do a "pre-parse" to
determine the universal type name.

Bill



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 (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe 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)