Local components

To implement thin components in the same address space we need a specific component model that defines local components and their interconnections. In Java there already exists such a thin component model (JavaBeans [2]), but in other languages like C++ and Python there are no such specifications.

So there is a need for a language independent local component model with mappings to many different programming languages. Instead of inventing another new component model, we use the CORBA Component Model in a local manner. By taking advantage of the adapter concept we can implement local components without a CORBA shell.

Figure B.2: Local and remote connection

As shown in Fig. B.2, there is a remote path and a local path between two component implementations. When running components in the same address space, there is no need for CORBA communication. Using the local path for connecting components significantly reduces the communication overhead.