Streams, protocols, documents and fragments

[Tom Harding]

David Megginson wrote:

> It's not necessarily the raw XML that will be delivered to the
> application, however

How about we create an architecture where it is?  I have a sample implementation of XP where an
endpoint fires an event when it has received a document.  The event wraps a DOM Document, so
the XML has been parsed, but any real processing, such as rendering, is still up to the
application.

This architecture doesn't really work with SAX, since you might attach long-running code to a
handler.  In this architecture, events don't occur at the element level; they correspond to the
network-level event of receiving a complete document.  You have lots of document "packets"
flying around.  What you do with them is up to you.

Tom Harding



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)