The Orbix Architecture - Distributed Object Computing (DOC) group

(defaulted) trailing argument which corresponds to the optional exception argument for theclient.A server programmer can create an instance of foo and provide the foo service by tellingOrbix that the server is now ready to receive bar requests. The simplest mainline is thus:// C++main () {foo_impl obj;CORBA::Orbix.impl_is_ready ();}Writing an Orbix Application - The Dynamic Invocation InterfaceUse of the IDL compiler, as above, requires a client to have available (possibly by dynamiclink loading) the marshalling stub code used to access any of the remote objects which itsuses.For some applications, this constraint may be too restrictive. CORBA specifies analternative, API-based, DII. Orbix provides the CORBA DII API. However, this API is, inour view, quite difficult to use and so we have provided an alternative stream based interface.Using the Orbix stream based DII the same client code as above can be written:char *result;long x;float y;char *z;TRY {// Initialise an object reference and a requestCORBA::ObjectRef target =CORBA::Object::_bind ("16716:Fred","qwerty", IT_X);CORBA::Request r(target, “op1”);// stream in the arguments, and make callr