... operations 3.1
  This is a somewhat idealistic assumption but sufficient for the scope of this example.

      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .

... languages 3.2
  The CORBA specification currently defines language mappings for a variety of high level languages like C, C++, Smalltalk, Cobol and Java.

      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .

... classes 3.3
  Note that C++ is currently the only language which is supported by MICO.

      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .

... dispatchers 3.4
  In this example the list contains only one dispatcher, namely for the Account-object. Later when we discuss interface inheritance this list will contain a dispatcher for each class in the inheritance hierarchy.

      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .

... this 3.5
  `mico-c++` and `mico-ld` are wrapper scripts for the C++ compiler and the linker, see section 4.6 for details

      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .

... machines 3.6
  Of course you can have some of the object implementations in the same process and some in other processes. The ORB hides the actual locations of the object implementations from the user

      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .

... BOA 3.7
  The Basic Object Adapter

      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .

... invocations 3.8
  You can make `run()` exit by calling the ORB method `shutdown()`, see section 4.3.4 for details.

      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .

... section 3.9
  The CORBA standard offers the ORB method `resolve_initial_references()` to obtain an object reference for the naming service. But that only moves the problem to the ORB instead of solving it.

      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .

... socket 3.10
  Unix-domain sockets are named, bidirectional pipes.

      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .

... reference 4.1
  IOR means Interoperable Object Reference

      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .

... registry 4.2
  See files `admin/code_set_registry.txt` and `admin/mico_code_set_registry.txt` in the MICO source tree.

      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .

... exiting 4.3
  `ird` is terminated by pressing `ctrl-c` or by sending it the `SIGTERM` signal

      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .

... implementations 4.4
  which basically means running a program that implements an object

      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .

... activated 4.5
  i.e. which program has to be run with which options and what activation policy has to be used for the implementation

      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .

... exiting 4.6
  `micod` is terminated by pressing `ctrl-c` or by sending it the `SIGTERM` signal

      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .

... server 4.7
  Usually one would define a new interface `ManagedObject` that contains the management operations and derive `Account` from `ManagedObject`. We don't do this here for ease of exposition.

      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .

... to 4.8
  The `-ORBImplRepoAddr` option is usually already in your `.micorc` file, so you do not have to specify it.

      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .

... needed 4.9
  Such a design pattern is called a factory.

      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .

... object 4.10
  If you delete lines 10 and 11 you will get the code for `create()` in a shared or persistent server.

      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .

... server 4.11
  Note that the CORBA 2 specification only gives you some vague idea of object persistence but omits any implementation details. That is why everything explained in this section is MICO-specific and will not work with other CORBA implementations.

      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .

... id 4.12
  See section 3.3.3 for details on repository ids.

      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .

... `FALSE` 4.13
  For instance by throwing an exception that is caught in `restore()`.

      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .

... other:4.14
  If supported by the C++ compiler, the `dynamic_cast<>` operator could be used instead.

      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .

... option:4.15
  If you omit this option, you will receive an ``Invalid Policy'' exception when trying to create a persistent POA.

      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .
      .