We're trying to use corba in our project in order to increase the robustness of whole system, separating critical from non critical activities in different processes.
We are currently using orocos 1.6 and, after some tries, we haven't success implementing two simple processes sending a heterogeneous struct.
We think that in commercial applications the robustness of the system is a must. Even in an earlier development stage, it's necessary to keep apart (in some kind of security domains) different tasks not direclty related. Separating them in different processes is, a priori, the esiest way to achieve it.
In this sceneario, it would be very convenient a complete example to illustrate an inter-process communication using Corba: the integration of the generated code from .idl, the addition of the type to the Orocos type system, the implementation of the AnyConversion and TransportRegistrator if any, etc.
Thanks in advance,
Carles Lopez
CORBA example in 1.6
On Thursday 16 April 2009 19:10:27 carles [dot] lopez [..] ... wrote:
> We're trying to use corba in our project in order to increase the
> robustness of whole system, separating critical from non critical
> activities in different processes.
>
> We are currently using orocos 1.6 and, after some tries, we haven't success
> implementing two simple processes sending a heterogeneous struct.
The class naming has been improved between 1.6 and 1.8, and some extra
debugging code was added. Apart from the complexity in understanding all the
involved classes, are you having compile-time problems or run-time problems ?
Peter
Corba and 1.8
I upgraded to version 1.8 and my dummy test is working now.
Here is attached the project showing the use of Corba to send a struct between two different processes. Remove the .patch extension and untar it.
It's not a high quality code nor totally portable but I hope it helps to clarify the issue.
For the brave who want to compile the code, change some paths in #include's and remove some #define's. Compile the .idl using your own IDL compiler and include the files in the client and the server side.
To launch the applications use the scripts included. Again, change them to fit to your system and corba configuration.
Happy re-coding!