- From: Assaf Arkin <arkin@intalio.com>
- Date: Mon, 24 Feb 2003 12:46:11 -0800
- To: "Walden Mathews" <waldenm@optonline.net>, <www-ws-arch@w3.org>
> -----Original Message----- > From: www-ws-arch-request@w3.org [mailto:www-ws-arch-request@w3.org]On > Behalf Of Walden Mathews > Sent: Monday, February 24, 2003 12:12 PM > To: Assaf Arkin; www-ws-arch@w3.org > Subject: Re: Snapshot of Web Services Glossary > > > > > What you are describing is the use of a synchronous protocol (HTTP) to > > synchronously transfer the state (you know it was received) for > asynchronous > > processing (later). > > > > I assume that later on you will receive a message indicating whether the > > request was processed. So at the higher-level (say choreography) the > > interaction involving request/response is synchronous, but each > individual > > operation is consider asynchronous, yet using a synchronous protocol to > > ensure receipt. > > I understand your explanation, but I don't think this advances the > effort, because the meaning of "synchronous protocol" is not clear, > at least not to me. How about: synchronous protocol - one which allows a request followed by a response synchronous only protocol - one which mandates a request be followed by a response arkin > > Walden
Received on Monday, 24 February 2003 15:47:48 UTC