Streams, protocols, documents and fragments

[David Megginson]

Tom Harding writes:
 > 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.

It all depends on your layering approach: personally, if typing
information is available, I'd rather use that to build optimised
internal representations first and hand those off to the application
-- a general-purpose DOM would be *extremely* inefficient for handling 
things like vector graphics or 3D worlds (to name only two), though it 
is always possible to expose their optimised object models through a
DOM interface later if necessary.


All the best,


David

-- 
David Megginson                 david at megginson.com
           http://www.megginson.com/

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)