Cart
[Home] [By Thread] [By Date] [Recent Entries]
Anders W. Tell wrote: ...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) ? > the protocol layer would be HTTP,SMTP etc. These protocols employ MIME. The process of content negotiation might provide something like: Content-type: application/xml; encoding="compressed-xml" I'm not sure about what DOM to DOM communication means, the DOM doesn't currently have any standard methods to even create XML documents, let alone provide communications support. Most parsers accept an href. You could propose a new protocol such as "x-xml:..." but better might be to request your encoding type in the HTTP request Accept: header and then check the response content-type. Jonathan Borden http://jabr.ne.mediaone.net xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i... 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@i... the following message; (un)subscribe xml-dev To subscribe to the digests, mailto:majordomo@i... the following message; subscribe xml-dev-digest List coordinator, Henry Rzepa (mailto:rzepa@i...)
|
