W3C home > Mailing lists > Public > public-ws-addressing-eds@w3.org > January to March 2006

2004/ws/addressing ws-addr-core.xml,1.120,1.121

From: Tony Rogers via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 08 Feb 2006 05:57:07 +0000
To: public-ws-addressing-eds@w3.org
Message-Id: <E1F6iKB-0007su-CG@lionel-hutz.w3.org>

Update of /sources/public/2004/ws/addressing
In directory hutz:/tmp/cvs-serv30256

Modified Files:
	ws-addr-core.xml 
Log Message:
Added the resolution of CR19 - removed text stating all interactions based on one-way.

Index: ws-addr-core.xml
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-core.xml,v
retrieving revision 1.120
retrieving revision 1.121
diff -C2 -d -r1.120 -r1.121
*** ws-addr-core.xml	8 Feb 2006 05:39:51 -0000	1.120
--- ws-addr-core.xml	8 Feb 2006 05:57:05 -0000	1.121
***************
*** 489,503 ****
                  and interfaces; business processes and e-commerce specifications, among others, can
                  also be used to define explicit contracts between the parties.</p>
!             <p> The basic interaction pattern from which all others are composed is "one-way". In
!                 this pattern a source sends a message to a destination without any further
!                 definition of the interaction. "Request-response" is a common interaction pattern
!                 that consists of an initial message sent by a source endpoint (the request) and a
!                 subsequent message sent from the destination of the request back to the source (the
!                 response). A response in this case can be either an application message, a fault, or
!                 any other message. Note, however, that reply messages may be sent as part of other
!                 message exchanges as well, and are not restricted to the usual single Request,
!                 single Response pattern, or to a particular WSDL transmission primitive or MEP. The
!                 contract between the interacting parties may specify that multiple or even a
!                 variable number of replies be delivered. </p>
              <p> The set of message addressing properties defined in this specification is sufficient
                  for many simple variations of one-way and request-response MEPs. More advanced MEPs
--- 489,502 ----
                  and interfaces; business processes and e-commerce specifications, among others, can
                  also be used to define explicit contracts between the parties.</p>
!             <p> In a one-way interaction pattern a source sends a message to a destination without
!                 any further definition of the interaction. "Request-response" is a common
!                 interaction pattern that consists of an initial message sent by a source endpoint
!                 (the request) and a subsequent message sent from the destination of the request back
!                 to the source (the response). A response in this case can be either an application
!                 message, a fault, or any other message. Note, however, that reply messages may be
!                 sent as part of other message exchanges as well, and are not restricted to the usual
!                 single Request, single Response pattern, or to a particular WSDL transmission
!                 primitive or MEP. The contract between the interacting parties may specify that
!                 multiple or even a variable number of replies be delivered. </p>
              <p> The set of message addressing properties defined in this specification is sufficient
                  for many simple variations of one-way and request-response MEPs. More advanced MEPs
Received on Wednesday, 8 February 2006 05:57:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:19:41 GMT