W3C home > Mailing lists > Public > xml-dist-app@w3.org > February 2001

Re: Intermediary Discussion

From: Bob Cunnings <cunnings@lectrosonics.com>
Date: Wed, 7 Feb 2001 13:38:15 -0700
Message-Id: <200102072038.NAA11514@lectrosonics.com>
To: xml-dist-app@w3.org
A topic of great interest:

Martin G. asked and James S. responded:

<snip>

> If a given intermediary is the 'target' for more than one 
> extension block in
> an XP message does a processing order need to be defined and 
> is so how do we
> define it?
> 

Yes, a processing order needs to be defined. As to how to go about doing
that, right now I have no suggestions.

</snip>

Just curious... what is the reasoning behind this assertion? I only ask because 
the (currently undefined) interface between XP processors and XP Module
processors will be profoundly influenced (I think) by this requirement. 
I suppose that in the simplest case, the extension blocks would be considered to 
be orthogonal to each other and the module processor(s) involved wouldn't care 
about ordering. On the other hand, of course it may be true that dependencies 
exist between the extension blocks. But why not let the XP processor sort all 
that out, since it has the required app-specific knowledge, and dispatch to the 
module processors as it sees fit? My worry is that such a rule might lead to 
fragility in the presence of intermediaries who manipulate the header contents.
They might then inadvertently break the ordering intended for "other" actors 
downstream. A sufficiently robust system might be quite complicated.

I am assuming that you are talking about application level extension block 
processing, not XP level. Please let me know if I am misunderstanding the scope 
of the question above.

RC
Received on Wednesday, 7 February 2001 15:38:27 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:58 GMT