Cart
[Home] [By Thread] [By Date] [Recent Entries]
> Then imagine you can write or communicate the object to other > systems simply with IO > operations with no processing involved. Then imagine that the IO > is async and very cheap and > that you are processing thousands of transactions per second, > most of which generate > fundamentally little processing steps. I just want to clarify my understanding of this thread: you're discussing a binary format which is analagous to the internal representation of an XML document (a DOM tree), and which can be stored, used and manipulated without revisiting the original XML text? Wouldn't a (undoubtedly naive) implementation of this be simply serialising the object graph to disk, or through an I/O stream? This is obviously easy in Java, and again is only obviously beneficial if the serialised object graph is more 'compact' (which I believe is at least partly behind your desire) than the original textual version? Just a brain check on my part ;) L. 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...)
|
