In <firstname.lastname@example.org> "Tuicear" <NA> writes:
>I have seen countless number of articles referring the advntages of CORBA.
>Can some CORBA experts/gurus tell us about its disadvantages?
Well, I'm not a guru, nor an expert, I'm more a pragmatic practician, but
here you go:
1. Firewall unfriendly. There's no real CORBA standard to bind an ORB and
it's clients to a port or a port range, there are (only) vendor specific
2. Regarded as complicated. This is in some parts a prejudice, in some parts
justificated: remote invocation of CORBA interfaces is at least as simple
as over XMLRPC (which is regarded as easy), but the C++ language mapping
predates the STL and features three different storage classes and
clumsy handling of sequences - there are other examples.
3. No standard to get the initial reference for the naming service. I don't
know why, but there never has been an OMG blessed standard to get an initial
reference for the naming service over the network. Of course, this results
in different solutions from different vendors, all using some kind of
4. No official perl mapping. There are at least two perl ORBs available as
open source, but neither the mapping is official, nor the implementations
are complete. Others may count this as an advantage, take your pick.
There are a couple of other script language ORBs, though, but perl
is still the favourite of sysadmins here in Europe, it seems.
Awaiting your comments,
Dipl. Inf. Ulrich Teichert|e-mail: Ulrich.Teichert@gmx.de
Stormweg 24 |listening to: Suicide Drive (The Deep Eynde)
24539 Neumuenster, Germany|Public Pervert (Interpol) Cauchemar (Opération S)