Next Previous Table of Contents
Common Object Request Broker Architecture, standard introduced by the OMG for distributed components that can be used independently of platform, implementation and operating system. CORBA itself is only the standard which requires a corresponding implementation that fulfills the requirements of the standard. KDE uses the MICO implementation, which provides a C++ interface to CORBA services.
Basic Object Adapter. Interface defined by the OMG, which offers fundamental operations for managing remote objects.
Common Object Services. Collection of standard services to simplify developing standard applications. Naming, Event and Lifecycle-services are a part of the COS collection.
Dynamic Invocation Interface, interface to execute dynamic invocations in opposition to static invocations (clent side)
Creation and execution of a request, whose signature is probably first known at runtime in opposition to static invocation.
Dynamic Skeleton Interface. Server side in opposition to a DII.
General-Inter-ORB-Protocol
Internet-Inter-ORB-Protocol
Implementation Repository
Interoperable Object Reference. The reference is specificated in the two parts GIOP and IIOP.
Interface Definition Language. C++-Syntax similar programming language to describe object interfaces. The implementation translates IDL's to their target programming language.
in CORBA, all exported methods and attributes of an object are called an interface, whereby these are defined in IDL. Elements which are not specified in the interface are not accessible by clients.
Interoperability Profile
free implementation of the CORBA standard. KDE's KOM/OpenParts technology is based on the MICO implementation.
Object Management Architecture
Object Management Group
Object Request Broker, abstract name for the communication service between clients and remote objects.
Portable Object Adapter. The POA extends the features the BOA provides; introduced in the CORBA 2.2 standard.
Next Previous Table of Contents