RE: Snapshot of Web Services Glossary

"Assaf Arkin" <[email protected]>
Newsgroups gmane.comp.web.services.ws-arch
Message-ID <[email protected]>


> -----Original Message-----
> From: [email protected] [mailto:[email protected]]On
> Behalf Of Walden Mathews
> Sent: Monday, February 24, 2003 12:12 PM
> To: Assaf Arkin; [email protected]
> 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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.