could you give some advice for choosing one of the open source C++/C
ORBs Tao, Mico, omniORB or Orbit2?
I know this was discussed many times in this group, but mostly at least
5 years ago (maybe with exception of
<j4Kdnavx0vT...@speakeasy.net>).
Fife years is a very long time in computer science, and I think the
products should have ripened a lot in the meantime (some might not have
changed at all, which says something, too).
So, what is the state of the C++ open source orbs today? Which one is
used most (Orbit2 I'd guess, because it is the work horse of the gnome
component model)? I have only experiences (very good) with the Java
JacORB, it's running rock solid.
I do know Arno Puder's corba matrix
(http://www.puder.org/corba/matrix/) and the benchmarks at
http://www.atl.external.lmco.com/projects/QoS/compare/dist_oo_compare_ipc.html
but I am more interested in some practical experiences.
Would you mind sharing some real life experiences, sucess stories,
deceptions or some anecdotes?
Thanks,
Juergen
we provide commercial support for TAO. We have a stable version,
classes, documentation, free patches, 24 by 7 support etc. If you want
industrial strength CORBA then TAO is it.
It is widely used by the US DOD (RT-CORBA is US Goverment required
spec)and so many contactors fund new features. Every year or so we
issue new versions with lots of new capabilities. We just added DDS to
TAO. the latest version also supports the CORBA component model.
I was not kidding when I said industrial strength. It is used in
airline reservation systems, credit checking, major technology
infrastructure providers, most telcos, and financial services
companies.
The community is very active. The platform support is very broad and
includes RT and embedded systems.
You said you liked JacORB. Tao users who need Java use JacORb so there
is good interoperability and comparable features as users harnmonize
them.
We also support JacORB, mostly adding new capabilties, training classes
etc, bug fixes are not that many.
I hope this helps.
regards Malcolm Spence
Dir. of Bus Devmnt.
OCI St. Louis MO 63141
TEL 1-314-579-0066
We've had great success with MICO over the years. We have it running on
Linux, Solaris, IRIX and even Unicos (Cray). It is very easy to compile
and is quite portable. It now has multi-threaded dispatch support and
has the naming, interface repository, event, property, time, and
implementation repository services bundled with it. Also, there is a
very good Tcl binding called Combat that works very well with MICO.
Karel Gardas of Object Security does a great job supporting MICO as well.
On the other hand, MICO doesn't currently support bidirectional IIOP,
doesn't have a Notification Service bundled, and is currently slower
than Tao and omniORB.
So, you might want to consider what other services, features and levels
of performance you think you'll need for your project so you won't have
to support multiple ORBs. (Not that that is all that hard.)
It'd be great if you published on the newsgroup what you decided and why?
Good Luck,
Rob
Juergen Weber wrote:
>Hi,
>
>could you give some advice for choosing one of the open source C++/C
>ORBs Tao, Mico, omniORB or Orbit2?
>
My company has had great success with omniORB. Here some of the reasons
it was selected:
- Very well documented
- Good example code to get you started
- Visual C++ is well supported, which is the compiler we are using
- Good mailing list at http://omniorb.sourceforge.net/list.html
- Proven code base, Olivetti, then AT&T
- Many features, so that you can take advantage of additional
functionality you become more familiar with CORBA, i.e. interceptors
and dynamic interfaces.
- Works well with Sun's Java ORB, any glitches have so far been on
Sun's side, for example their IOR string is non-standard, however no
show-stoppers.
- open source - even though the ones you mention are all oss anyway,
I'll mention this since it is an important reason. Our company is
heavily using open source software (mostly for Java, but a few tools
such as WinSQL), and this definitely takes away some roadblocks to get
your software selected.
Some additional contacts available from Who Is Using OmniORB:
http://www.omniorb-support.com/omniwiki/WhoIsUsingOmniorb
-Mike