W3C home > Mailing lists > Public > www-ws-arch@w3.org > February 2003

Re: Sync Definition #2 (corrected)

From: Walden Mathews <waldenm@optonline.net>
Date: Wed, 26 Feb 2003 22:28:46 -0500
To: Assaf Arkin <arkin@intalio.com>, Ugo Corda <UCorda@SeeBeyond.com>, www-ws-arch@w3.org
Message-id: <008401c2de10$56e9c880$1702a8c0@WorkGroup>
RE: Sync Definition #2 (corrected)Arkin,

I don't understand where your fascination with these permutations
is coming from.  I thought the goal was to define the two terms, one
definition each, and let it go at that (if possible).

Walden
  ----- Original Message ----- 
  From: Assaf Arkin 
  To: Ugo Corda ; www-ws-arch@w3.org 
  Sent: Wednesday, February 26, 2003 3:51 PM
  Subject: 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. 
Received on Wednesday, 26 February 2003 22:31:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:15 GMT