RE: Friendly amendment to friendly amendment (was RE: Friendly amendm ent #2c [Re: Straw poll on "synchronous" definitions]
"Cutler, Roger (RogerCutler)" <[email protected]> Mon, 17 Mar 2003 15:17:56 -0600
| Newsgroups | gmane.comp.web.services.ws-arch |
|---|---|
| Message-ID | <7FCB5A9F010AAE419A79A54B44F3718E01624BB5@bocnte2k3.boc.chevrontexaco.net> |
This is a multi-part message in MIME format. ------_=_NextPart_001_01C2ECCA.AE253CC2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable I'd be willing to go with this one. =20 -----Original Message----- From: Champion, Mike [mailto:[email protected]]=20 Sent: Sunday, March 16, 2003 10:18 AM To: [email protected] Subject: Friendly amendment to friendly amendment (was RE: Friendly amendm ent #2c [Re: Straw poll on "synchronous" definitions] =20 -----Original Message----- From: Anne Thomas Manes [mailto:[email protected]] Sent: Saturday, March 15, 2003 6:12 PM To: Walden Mathews; Christopher B Ferris; [email protected] Subject: RE: Friendly amendment #2c [Re: Straw poll on "synchronous" definitions] =09 =09 The biggest issue I have with Ugo's definition (and all the others) is that they tie synchrony with blocking versus non-blocking. Synchronous means "at the same time". Asynchronous means "not at the same time". Whether or not the sender has to wait idly for a response is a separate issue.=20 =20 An interaction (one-way, two-way, or multi-way) is synchronous if the sender and receiver must communicate at the same time (the reciever must be available to receive the message when the sender sends it). A one-way message is asynchronous if the sender and receiver do not need to communicate at the same time (the message may be stored and delivered at a later time). =20 I must say that I like Anne's wording that synchronous means that "the receiver must be available to receive the message" better than notions of blocking or simultaneity. What about changing Ugo's suggestion to: =20 Asynchronous: A request/response interaction is said to be asynchronous when the request and response are chronologically and procedurally decoupled. In other words, the client agent can process the response at some indeterminate point in the future when its existence is discovered, for example, by polling, notification by receipt of another message, etc.=20 =20 Synchronous: A request/response interaction is said to be synchronous when the client agent must be available to receive and process the response message from the time it issues it issues the initial request until it is actually received or some failure condition is determined. The exact meaning of "available to receive the message" depends on the characteristics of the client agent (including the transfer protocol it uses); it may, but does not necessarily, imply tight time synchronization, blocking a thread, etc. =20 =20 ------_=_NextPart_001_01C2ECCA.AE253CC2 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD><TITLE>Message</TITLE> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Dus-ascii"> <META content=3D"MSHTML 6.00.2719.2200" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><SPAN class=3D644311721-17032003><FONT face=3DArial color=3D#0000ff = size=3D2>I'd be=20 willing to go with this one.</FONT></SPAN></DIV> <DIV><SPAN class=3D644311721-17032003></SPAN> </DIV> <DIV></DIV> <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr = align=3Dleft><FONT face=3DTahoma=20 size=3D2>-----Original Message-----<BR><B>From:</B> Champion, Mike=20 [mailto:[email protected]] <BR><B>Sent:</B> Sunday, March = 16,=20 2003 10:18 AM<BR><B>To:</B> [email protected]<BR><B>Subject:</B> = Friendly=20 amendment to friendly amendment (was RE: Friendly amendm ent #2c [Re: = Straw poll=20 on "synchronous" definitions]<BR><BR></FONT></DIV> <DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT> </DIV> <BLOCKQUOTE dir=3Dltr=20 style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px = solid; MARGIN-RIGHT: 0px"> <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT = face=3DTahoma=20 size=3D2>-----Original Message-----<BR><B>From:</B> Anne Thomas Manes=20 [mailto:[email protected]]<BR><B>Sent:</B> Saturday, March 15, 2003 6:12=20 PM<BR><B>To:</B> Walden Mathews; Christopher B Ferris;=20 [email protected]<BR><B>Subject:</B> RE: Friendly amendment #2c [Re: = Straw=20 poll on "synchronous" definitions]<BR><BR></FONT></DIV> <DIV><SPAN class=3D460020123-15032003><FONT face=3DArial = color=3D#0000ff size=3D2>The=20 biggest issue I have with Ugo's definition (and all the others) is = that they=20 tie synchrony with blocking versus non-blocking. Synchronous means "at = the=20 same time". Asynchronous means "not at the same time". Whether or not = the=20 sender has to wait idly for a response is a separate issue.=20 </FONT></SPAN></DIV> <DIV><SPAN class=3D460020123-15032003><FONT face=3DArial = color=3D#0000ff=20 size=3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D460020123-15032003><FONT face=3DArial><FONT = color=3D#0000ff><FONT=20 size=3D2>An interaction (one-way, two-way, or multi-way) is = synchronous if=20 the sender and receiver must communicate at the same time (the = reciever must=20 be available to receive the message when the sender sends it). A = one-way=20 message is asynchronous if the sender and receiver do not need to = communicate=20 at the same time (the message may be stored and delivered at a later=20 time). <SPAN=20 = class=3D299350016-16032003> </SPAN></FONT></FONT></FONT></SPAN></DIV= ></BLOCKQUOTE> <DIV dir=3Dltr><SPAN class=3D460020123-15032003><FONT face=3DArial><FONT = color=3D#0000ff><FONT size=3D2><SPAN class=3D299350016-16032003>I must = say that I like=20 Anne's wording that synchronous means that "the receiver must be = available to=20 receive the message" better than notions of blocking or=20 simultaneity. What about changing Ugo's suggestion=20 to:</SPAN></FONT></FONT></FONT></SPAN></DIV> <DIV dir=3Dltr><SPAN class=3D460020123-15032003><FONT face=3DArial><FONT = color=3D#0000ff><FONT size=3D2><SPAN=20 class=3D299350016-16032003></SPAN></FONT></FONT></FONT></SPAN> </DIV= > <DIV dir=3Dltr><SPAN class=3D460020123-15032003><FONT face=3DArial><FONT = color=3D#0000ff><FONT size=3D2><SPAN = class=3D299350016-16032003>Asynchronous: A=20 request/response interaction is said to be asynchronous<BR>when the = request and=20 response are chronologically and procedurally decoupled. In = other<BR>words, the=20 client agent can process the response at some indeterminate point = in the=20 future when its existence is discovered, for example, by = polling,=20 notification by receipt of another message,=20 etc. </SPAN></FONT></FONT></FONT></SPAN></DIV> <DIV dir=3Dltr><SPAN class=3D460020123-15032003><FONT face=3DArial><FONT = color=3D#0000ff><FONT size=3D2><SPAN=20 class=3D299350016-16032003></SPAN></FONT></FONT></FONT></SPAN> </DIV= > <DIV dir=3Dltr><SPAN class=3D460020123-15032003><FONT face=3DArial><FONT = color=3D#0000ff><FONT size=3D2><SPAN=20 class=3D299350016-16032003>Synchronous: A request/response = interaction=20 is said to be synchronous when the client agent must be available to = receive and=20 process the response message from the time it issues<BR>it issues the = initial=20 request until it is actually received or some failure condition is = determined.=20 The exact meaning of "available to receive the message" depends on the=20 characteristics of the client agent (including the transfer protocol it = uses);=20 it may, but does not necessarily, imply tight time synchronization, = blocking a=20 thread, etc.</SPAN></FONT></FONT></FONT></SPAN></DIV> <DIV dir=3Dltr><SPAN class=3D460020123-15032003><FONT face=3DArial><FONT = color=3D#0000ff><FONT size=3D2><SPAN=20 class=3D299350016-16032003></SPAN></FONT></FONT></FONT></SPAN> </DIV= > <DIV dir=3Dltr><SPAN class=3D460020123-15032003><FONT face=3DArial><FONT = color=3D#0000ff><FONT size=3D2><SPAN=20 class=3D299350016-16032003></SPAN></FONT></FONT></FONT></SPAN> </DIV= ></BODY></HTML> =00 ------_=_NextPart_001_01C2ECCA.AE253CC2--