RE: Sync Definition #2 (corrected)

RE: Sync Definition #2 (corrected)Actually, yours can be easily phrased in
terms of mine:

A synchronous interaction (= reqeust/response) is communicated
asynchronously when the request and response are chronologically decoupled.
In other words ...

A synchronous interaction is communicated synchronoulsy if the reverse could
be said.

Which of course begs the question, what about an asynchronous interaction.
Say I just send a message but don't expect a response?

An asynchronous interaction (= send or receive) is communicated
asynchronoulsy when the sender does not have to wait for the receiver to
receive the message.

An asynchronous interaction is communicated synchronoulsy if the reverse
could be said.

arkin
  -----Original Message-----
  From: Ugo Corda [mailto:UCorda@SeeBeyond.com]
  Sent: Wednesday, February 26, 2003 12:46 PM
  To: Assaf Arkin; www-ws-arch@w3.org
  Subject: RE: Sync Definition #2 (corrected)


  Well, it's a matter of definitions, and evidently yours does not
correspond to mine. I hope people will vote soon so that we can put this
issue behind ...

  Ugo
    -----Original Message-----
    From: Assaf Arkin [mailto:arkin@intalio.com]
    Sent: Wednesday, February 26, 2003 12:15 PM
    To: Ugo Corda; www-ws-arch@w3.org
    Subject: RE: Sync Definition #2 (corrected)


    I think you have just defined a synchronous interaction
(request/response, see formal definition) in terms of an asynchronous
transport (i.e. one that does send and receive actions independently).

    arkin
      -----Original Message-----
      From: www-ws-arch-request@w3.org [mailto:www-ws-arch-request@w3.org]On
Behalf Of Ugo Corda
      Sent: Wednesday, February 26, 2003 7:36 AM
      To: Ugo Corda; www-ws-arch@w3.org
      Subject: RE: Sync Definition #2 (corrected)


      Asynchronous:
      A request/response interaction is said to be asynchronous when the
request and response are chronologically decoupled. In other words, the
client agent does not have to "wait" for the response once it issues the
initial request. The exact meaning of "not having to wait" depends on the
characteristics of the client agent (including the transfer protocol it
uses). Examples include receiving the response on a different thread, on a
different socket, on a different end-point, by polling the server, etc.

      Synchronous:
      The opposite of asynchronous.