SOMA Interoperability (2) |
The interoperability features are obtained via the CORBABridge add-on (see Figure 2), which is composed of two distinct modules: the first one (CORBA C/S) simplifies the design of SOMA entities as CORBA clients/servers; the second one (MASIFBridge) implements the MASIF functionality. Since MASIF implementation can introduce a heavy overhead for the execution place, we have decided not to extend all the places with this module: our guideline is that only one place per domain should be extended with MASIFBridge; on the other hand, the CORBA C/S module is lightweight, and many places in the same domain may use it to access to the CORBA bus, either for calling external services or for registering as servers. Any SOMA agent, resident at a CORBA C/S extended place, is able to act as a CORBA client/server through both static (IDL stub/skeleton) and dynamic (DII/DSI) invocations/registrations. |
|
We are currently testing SOMA interoperability by designing applications in which our mobile agents cooperate with mobile agents from other MA MASIF-compliant platforms, such as Grasshopper.
In considering interoperability, SOMA does also take into account the security problems that stem from interacting with external components and provides solutions compliant with both CORBA security services and MASIF security features.
Page
updated on
|
In
case of problems, or if you find any bug, please contact us.
|