Cart
[Home] [By Thread] [By Date] [Recent Entries]
David Megginson wrote: > 1. Use a non-XML mechanism for separating XML packets -- that way, > there's not a tight dependency between the stream-handler and the > parser (the stream handler knows the bounds of each packet without > doing any XML parsing). What bit sequence would you use as a separator and how would you ensure that no conceivable encoding would produce it spuriously? > 2. Separate information about the packages from the packets > themselves. The information could be linear, or it could itself be > XML packets of a different sort. You should not have to parse an > entire packet to know its sequencing, etc. How could you terminate a document with another doc element? The only thing allowed after all legitimate Misc markup at the end of a document is more Misc markup. > Putting a PI in the XML packet itself seems a little awkward to me. How about thinking of it as a "network-ready" document? Or if you like, explicitly define a "packet" as such a document. Tom Harding 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...)
|
