Issue 4942: CORBA's operation invocation styles.                                                                                                                                                                    (action-semantics-ftf)
Source:  (, )
Nature: Uncategorized Issue
Severity: 
Summary: [Joaquin Miller] Does the messaging mode support CORBA's messaging styles?

Joaquin,

 > But the three ways of invoking a procedure in CORBA are:
 > 
 > One is synchronous, which works just as you write above.
 > 
 > The second is asynchronous or one-way, which is not exactly
 > the same as you describe above for the action semantics.   
 > But close enough, perhaps.   

I can't tell the difference.


 > The third has the silly name, deferred synchronous; it is a kind
 > of asynchronous invocation. 

The CORBA spec says this is a synchronous operation called
asynchronously, but the caller still has the option to get the results
at a later time.  Action semantics does not support this.  The
workaround would be complicated.
Resolution: decline
Revised Text: 
Actions taken:
March 5, 2002: received issue
December 11, 2002: closed issue
Discussion: 
Use ordinary parallel flows and resynchronize the flows to model this
End of Annotations:=====
Summary: CORBA's operation invocation styles.

Text: 

[Joaquin Miller] Does the messaging mode support CORBA's messaging
styles?

Joaquin,

 > But the three ways of invoking a procedure in CORBA are:
 > 
 > One is synchronous, which works just as you write above.
 > 
 > The second is asynchronous or one-way, which is not exactly
 > the same as you describe above for the action semantics.   
 > But close enough, perhaps.   

I can't tell the difference.


 > The third has the silly name, deferred synchronous; it is a kind
 > of asynchronous invocation. 

The CORBA spec says this is a synchronous operation called
asynchronously, but the caller still has the option to get the results
at a later time.  Action semantics does not support this.  The
workaround would be complicated.

Conrad