- From: Hugo Haas <hugo@w3.org>
- Date: Wed, 4 Apr 2001 09:10:43 -0400
- To: xml-dist-app@w3.org
* Jean-Jacques Moreau <moreau@crf.canon.fr> [2001-04-04 14:21+0200] > R802 may indeed lead to some representation that physically > partitions the message, and header/body is one such representation; > but then it only helps the final receiver "process XMLP blocks > intended for them without processing the entire message", *not* the > intermediaries. I might be missing something here; both intermediaries and the final destination can have: - a well-defined set of blocks addressed to them and arranged so that they do not process (i.e. parse) what's not theirs. For intermediaries, they can stop once they know that the rest is for the final destination. - references to other blocks that may be out of this set (as pointed out by Mark) that defeat this ordering. - references to trailers that would be require them to parse the whole thing. Could you explain what difference between the final receiver and an intermediary makes you say that? I am unsure about what is intended by "processing" in R802... Since Henrik talked about it for the Header/Body distinction, I am assuming that it really means "parsing". -- Hugo Haas - W3C mailto:hugo@w3.org - http://www.w3.org/People/Hugo/ - tel:+1-617-452-2092
Received on Wednesday, 4 April 2001 09:10:45 UTC