- From: Champion, Mike <Mike.Champion@SoftwareAG-USA.com>
- Date: Mon, 24 Feb 2003 14:49:48 -0700
- To: www-ws-arch@w3.org
> > > -----Original Message----- > From: Cutler, Roger (RogerCutler) > [mailto:RogerCutler@chevrontexaco.com] > Sent: Monday, February 24, 2003 4:31 PM > To: Assaf Arkin; Walden Mathews; Ugo Corda; www-ws-arch@w3.org > > > OK, I think I get it. Thanks. It seems that the scope (if > that is the correct word) that one is considering is really important. > > It looks to me like a relatively large number of people on > this thread are pretty much on the same page. So can > somebody suggest specific, simple entries to put in the > Glossary for "synchronous" and "asynchronous" -- and whatever > other terms might seem required? And/or some discussion for > the document itself? This seems close enough for our immediate purposes. Truly precise definitions will not be nailed down EVER, because the meanings will change as the world around us changes. http://whatis.techtarget.com/definition/0,,sid9_gci213080,00.html "2) In program-to-program communication, synchronous communication requires that each end of an exchange of communication respond in turn without initiating a new communication. A typical activity that might use a synchronous protocol would be a transmission of files from one point to another. As each transmission is received, a response is returned indicating success or the need to resend. Each successive transmission of data requires a response to the previous transmission before a new one can be initiated. Synchronous program communication is contrasted with asynchronous program communication. " " In computer programs, asynchronous operation means that a process operates independently of other processes, whereas synchronous operation means that the process runs only as a result of some other process being completed or handing off operation. A typical activity that might use a synchronous protocol would be a transmission of files from one point to another. As each transmission is received, a response is returned indicating success or the need to resend. Each successive transmission of data requires a response to the previous transmission before a new one can be initiated. "
Received on Monday, 24 February 2003 16:50:29 UTC