Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
As far as I know there were problems with incompatible CORBA implementations in the past resulting from different interpretations of the specification. How is the situation today? Can I expect two different implementations to interact without problems?
I worked with corba stuff for the last 8 years. Its a standard (ASAM ODS OO API) and uses Corba to implement the API between server and clients.
We din’t find incompatibilities till a long time. (java, jorb, mico, omniorb / C++ / Java)
When we started there were mainly problems with the nameservices (different port, …) but we didn’t figure out any real incompatibility till then.
I think the difference between the different orb implementations may be the features that are represented by the implementation.
What is still there is that speed of the different implementations differ.