[
Lists Home |
Date Index |
Thread Index
]
- From: "Anders W. Tell" <anderst@toolsmiths.se>
- To: David Megginson <david@megginson.com>
- Date: Sat, 27 Mar 1999 18:34:59 +0100
David Megginson wrote:
> In general, though, what we need is a transport layer that takes care
> of things like this for us. Document type designers should optimise
> for readability and usability, and let protocol designers worry about
> the optimisations.
In general I agree especially with that Document Type creator should not
be doing "manual optimizations". However I in the case of DOM to DOM
communication its possible to to much better than using XML text a content carrier.
In this case the question arises, where is the protocol interface ?
Is it an interface that accepts a arbitrary byte stream and transports opaque data
to a receiver (A) or is it a an interface that accepts a DOM tree and sends it
ot a receiver (B) ?
(A)
DOM --> [streamifyXML] --> XML text -->[protocolInterface] -->something smaller,faster (gzip,
FastML,...)
==communicate==>
something smaller,faster --> [protocolInterface] --> XML text ->[SAX] --> DOM
(B)
DOM --> [protocolInterface] -->something smaller (gzip)
==communicate==>
something smaller --> [protocolInterface] -->DOM
/anders
--
/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
/ Financial Toolsmiths AB /
/ Anders W. Tell /
/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
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/ and on CD-ROM/ISBN 981-02-3594-1
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)
|