next up previous
Next: 3.6.4 Procedure lookup Up: 3.6 Messaging Actions Previous: 3.6.2 Consideration for distributed

3.6.3 Procedures

Procedures themselves are not actions, but rather combination of actions. A requested object receiving a message usually implies a procedure is to be executed. Note that an invocation can not directly execute an action, but only a procedure.

The concept of procedures in action semantics provides a certain level of modularity. Procedures are self-contained. The execution of a procedure is not allowed to access any global variables or static variables. Instead, all the variables are contained in an object in the form of attributes.

There is no means to explicitly execute part of a procedure from the requesting object. A procedure is regarded as an entity, which accepts input and produces output (like actions). The input is taken from the attributes of the request message. For synchronous invocation, the output serves as the return value; for asynchronous invocation, the output is simply ignored.



Thomas Feng 2003-04-18