Issue 2005: Synchronous action (action-semantics-ftf) Source: (, ) Nature: Clarification Severity: Significant Summary: Summary: A synchronous action is defined as a request where the sending object pauses to wait for results. Synonym: synchronous request [OMA]. 1) The OMA is not specific on this issue, but the understanding in CORBA is that a request is only specific with respect to a thread. - So, in UML, does the sending *object* truly pause to wait for results? - Or is it just a *thread* of that object that pauses for results? (in that case, the definition should be clarified) 2) Another possible interpretation of a synchronous action is that such a request is always associated with a response (contrarily to an asynchronous request which has no associated response -?-). The sending object has then an obligation to collect that response. If that interpretation was true, then synchronous action would map to both synchronous request and def Resolution: Fixed in adopted spec Revised Text: Actions taken: September 28, 1998: received issue July 22, 1999: Deferred to UML 1.4/2.0. March 5, 2002: moved from UML RTF ro Action Semantics FTF October 23, 2002: closed issue December 11, 2002: closed issue Discussion: The action semantics uses the second intepretation, see section 2.22.3 of the adopted spec End of Annotations:===== Return-Path: Date: Mon, 28 Sep 1998 12:58:15 -0400 From: www To: juergen@omg.org, web-incoming@omg.org Subject: WWW Form output Name: Guy GENILLOUD Company: EPFL Email: guy.genilloud@di.epfl.ch Specification: UML Semantics Section: Appendix B Formal #: ad/97-08-04 Version: 1.1 (or 1.0 ?) Revision_Date: Page: 158 Nature: Clarification Severity: Significant full_desc: A synchronous action is defined as a request where the sending object pauses to wait for results. Synonym: synchronous request [OMA]. 1) The OMA is not specific on this issue, but the understanding in CORBA is that a request is only specific with respect to a thread. - So, in UML, does the sending *object* truly pause to wait for results? - Or is it just a *thread* of that object that pauses for results? (in that case, the definition should be clarified) 2) Another possible interpretation of a synchronous action is that such a request is always associated with a response (contrarily to an asynchronous request which has no associated response -?-). The sending object has then an obligation to collect that response. If that interpretation was true, then synchronous action would map to both synchronous request and deferred synchronous request. (OMA v3, June 13 1997, p.78). submit: Submit Issue Report Return-Path: X-Sender: genillou@dimail.epfl.ch Date: Mon, 28 Sep 1998 19:00:51 +0200 To: juergen@omg.org From: Guy GENILLOUD Subject: issue on synchronous action in UML Juergen, I just submitted an issue in which I wrote something like "only specific w.r.t a given thread". I meant to write "only synchronous w.r.t a given thread". Can you make the correction of my issue. Thanks Guy -------------------------------------------------------------------- Dr. Guy Genilloud Institute for computer Communications and Applications (ICA) Swiss Federal Institute of Technology (EPFL) tel: +41 21 693 46 57 CH-1015 Lausanne, SWITZERLAND fax: +41 21 693 47 01 --------------------------------------------------------------------