| Previous | Table of Contents | Next |
An interface is available, which allows dynamic handling of object invocations. That is, rather than being accessed through
a skeleton that is specific to a particular operation, an object’s implementation is reached through an interface that provides
access to the operation name and parameters in a manner analogous to the client side’s Dynamic Invocation Interface. Purely
static knowledge of those parameters may be used, or dynamic knowledge (perhaps determined through an Interface Repository)
may be also used, to determine the parameters.
The implementation code must provide descriptions of all the operation parameters to the ORB, and the ORB provides the values
of any input parameters for use in performing the operation. The implementation code provides the values of any output parameters,
or an exception, to the ORB after performing the operation. The nature of the dynamic skeleton interface may vary substantially
from one programming language mapping or object adapter to another, but will typically be an up-call interface.
Dynamic skeletons may be invoked both through client stubs and through the dynamic invocation interface; either style of client
request construction interface provides identical results.