The CORBA specification defines two MECHANISMS for invoking operations on a CORBA Object. Functionaly, the two mechanisms provide the same capabilities. They allow basically the IDL defined operations on the CORBA object to be invoked, allow program variables to be passed to the operation as inbound parameters, and allow return VALUES or out parameters to be passed from the server to the client. The first mechanism is known as the Static Invocation Interface (SII), the other is known as DYNAMIC Invocation Interface . Developers of client applications which USE SII must know the name of the operation, and all parameters/return TYPES prior to program compilation. The actual operation names and parameters/return values are in effect hard coded into the application source code.

The CORBA specification defines two mechanisms for invoking operations on a CORBA Object. Functionaly, the two mechanisms provide the same capabilities. They allow basically the IDL defined operations on the CORBA object to be invoked, allow program variables to be passed to the operation as inbound parameters, and allow return values or out parameters to be passed from the server to the client. The first mechanism is known as the Static Invocation Interface (SII), the other is known as Dynamic Invocation Interface . Developers of client applications which use SII must know the name of the operation, and all parameters/return types prior to program compilation. The actual operation names and parameters/return values are in effect hard coded into the application source code.