- From: Cutler, Roger (RogerCutler) <RogerCutler@chevrontexaco.com>
- Date: Tue, 25 Feb 2003 10:49:01 -0600
- To: "Dale Moberg" <dmoberg@cyclonecommerce.com>, "Walden Mathews" <waldenm@optonline.net>, "Assaf Arkin" <arkin@intalio.com>, www-ws-arch@w3.org
Oh goody. Another entry in the synchronicity sweepstakes, clearly different from at least some of the previous ones. I really like all of them -- but I don't think that they are the same and I don't think that understanding each one of the approaches is leading to convergence. I think that somehow we've either got to converge on one approach, even if that decision is made arbitrarily, or agree to use the terms with some sort of modifiers that indicate which of the meanings is intended. -----Original Message----- From: Dale Moberg [mailto:dmoberg@cyclonecommerce.com] Sent: Tuesday, February 25, 2003 10:17 AM To: Walden Mathews; Assaf Arkin; www-ws-arch@w3.org Subject: RE: Snapshot of Web Services Glossary on Response types I normally interpret people to mean the following when they talk about the difference between a synchronous or asynchronous _response_. There are lots of other meanings to these terms as applied to other entities. I would not disagree with people lamenting the terminology selected, but it is a done deal at this point, IMO. A web service response is said to be synchronous iff it is returned using the same network connection used in sending the request to which it is a response. [This implies that only one URL would be needed for request-response MEP when the response is synchronous and uses a transfer protocol that has URLs. It also implies that the request and response occur within the interval of time that the network connection exists. Also, there is overhead in setting up only one TCP connection when TCP is used, and since we are talking about IP _connections_ that will be almost always the case.] A web service response is said to asynchronous iff it is returned using a network connection that is distinct from that used for sending the request to which it is a response. [Implications: Two URLs are needed to configure a request-response MEP when the response is synchronous. The response connection may occur while the request connection is still open or after it is closed. For TCP-based transfer protocols, two connection setups will be needed.]
Received on Tuesday, 25 February 2003 12:04:59 UTC