RE: [xml-dev] Nested Documents (was: XML 2.0)
> If you want to defend yourself against unreliability in the transport layer
> and below, you could (a) use a more reliable transport layer, or (b) add a
> checksum or signature.
Is (b) really feasible? You really want to take on the burden of xml canonicalization?
And (a) isn't an answer -- you're log-reading program has no way of knowing if the log-writer is done or if the disk filled up just as it was trying to log ENOSPC. :) Less flippantly, multiple roots mean the producer, transport, and consumer become more tightly intertwined, which doesn't seem like a good thing.
Doesn't seem like a good tradeoff just to read logfiles, especially when there's already work-arounds (which don't make the world catch on fire).
/r$
--
STSM, DataPower Chief Programmer
WebSphere DataPower SOA Appliances
http://www.ibm.com/software/integration/datapower/