CIAO Release Information and TODOs


Current Status

  1. Latest News

  2. Status of individual modules

    Modules Status
    CCM Core We are currently working on a prototype that enables remote component installation using the CCM ComponentInstallation interface, a component server implementation. Since we still don't have a CIDL implementation, we will also write up an example to show how the code should be generated in both CCIDL compiler and provide example component implementations. There exists 3 libraries in CCM Core.
    1. CIAO_Client: contains the client side stubs for CCMObject. All client programs that use CCMObject must link to this library.
    2. CIAO_Container: contains the interface definitions and CIAO's container implementation. All component implementations must link to this library.
    3. CIAO_Server: contains the stubs to access deployment framework. We'll need to use this to implement the deployment mechanism.
    TAO_IDL TAO_IDL has been extended to handle and generate all the component related keywords but import. We are currently using the generated mapping, in combination to manually simulation of CIDL generated code to implement CCM component. TAO_IDL Check out TAO IDL compiler for more details.
    CIDL (Component Implementation Defintion Language) Compiler An implementation that supports a subset of CIDL appropriate for DRE systems has been implemented. We do not have immediate plans to integrate Persistence State Service into the CIAO CIDL compiler. At present we support only a simple construct like the following:
            module component_composite_name {
              composition service component_home_executor {
                implements component_home;
                manages component_executor;
              };
            };
    
    The compiler generates operation implementations inherited from following interfaces:
    • Navigation
    • Receptacle
    • Event
    • CCMObject
    • Component specific context
    • Executor

  3. TAO Modules required by CIAO: We currently don't have a target set up in TAO's make system to build CIAO required module only, so you need to do this yourself. (BTW, we only support the use of dynamic linked libraries, at least for now.) Here is a list of necessary TAO modules in order of dependencies:
    1. TAO Main library.
    2. PortableServer
    3. orbsvcs/orbsvcs/Security
    4. IFR_Client


Project Outlook

This to-do list is currently arranged in chronological order, i.e., we group features that are expected to be available in certain release together. All interfaces and types are under Components module namespace if not specified explicitly.