Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved


Client Adapters : Client Adapter

Client Adapter
This section establishes the basic requirements that your client adapter implementations must meet so that they can be plumbed into a stream.
The ClientAdapter Module
The interface exposing the implementation of the module must inherit from provca::ClientAdapter.
The module instance is responsible for handling administration operations and module-scoped configuration attributes. It also features accessors to runtime objects like the session manager and protocol message flow proxies.
The provca::ClientAdapter module uses four ports which are added by provca::ClientAdapter when an instance of the ClientAdapter interface is created, as shown in the following table:
The Client Adapter Interface
You can use the following IDLos as a framework for your client adapter interface:
package tcpca
{
interface ClientAdapter : provca::ClientAdapter
{
[ virtual ]
void enable();

[ virtual ]
void disable();

[ virtual ]
void lock();

[ virtual ]
void unlock();

[ virtual ]
void configure(
in provca::Config i_config)
raises (provca::OperationFailed);
};
};
The Client Adapter Configuration
Client adapters are configured by instantiating the provca::Config interface and loading the configuration instance in the client adapter.
The provca::Config references several other configuration interfaces and factories that can be used to reference custom implementations of SessionFactory and others.
Derived client adapters may need to add their own configuration parameters. In this case, an interface inheriting the basic configuration interface is needed and the configure operation of the client adapter must be overloaded.
You can use the following IDLos as a framework for your configuration interface:
package tcpca
{
interface Config : provca::Config
{
};
};

Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved