- From: Henrik Frystyk Nielsen <henrikn@microsoft.com>
- Date: Mon, 3 Jun 2002 15:49:49 -0700
- To: <noah_mendelsohn@us.ibm.com>
- Cc: "Christopher Ferris" <chris.ferris@sun.com>, "Jean-Jacques Moreau" <moreau@crf.canon.fr>, <xml-dist-app@w3.org>
As MEPs are features and hence mentioned in another section, I tried to not mix them into the basic processing model, but I think a reference would be fine. What about the following tweak: <noah tweak="1"> This section defines the SOAP distributed processing model. The processing model defined in this section applies to a single SOAP message independent of any other SOAP message; it makes no claim as to whether a given entity acting as a SOAP node for the processing of one (or more) messages need do so for others. While the specification of individual SOAP features (see 3.1 SOAP Features) such as MEPs may call for groups of messages to be processed in certain combinations, this is not part of the processing model defined in this section. </noah> ><henrik> >This section defines the SOAP distributed processing >model. The processing model defined in this section >applies to a single SOAP message independent of any >other SOAP message. ><henrik> > ><noah> >This section defines the SOAP distributed processing >model. The processing model defined in this section >applies to a single SOAP message independent of any >other SOAP message; this specification makes no claim >as to whether a given entity acting as a SOAP node >for the processing of one (or more) messages need >do so for others, except insofar as particular MEPs >(see XXX) MAY call for groups of messages to be processed >in combination. ></noah> Henrik
Received on Monday, 3 June 2002 18:51:16 UTC