Vista comes with APIs for condition variables and reader-writer locks so you don't have to spend 15 minutes writing your own. You are not a frequent reader of comp.programming.threads, aren't you?
Actually it is difficult to find good alternatives to CORBA for high performance and/or mission critical distributed applications.
ICE, the middleware created by the company where the author of the article works, is very good.
The downsides:
- It is proprietary
- It is not free for commercial applications (this is not bad per se)
Most of the shortcomings of CORBA depicted by Michi Henning are true.
But some of them are avoidable.
These are some pros for CORBA:
- Many freeware implementations (TAO, OmniOrb, JacOrb, etc)
- Very good performances
- Good support (both from public forums and private companies - three or four companies, for instances, offer support for TAO)
- Interoperability with everything. Java is compatible out of the box (even if the JDK ORB is acceptable only on the client side). The excellent IIOP.NET (http://iiop-net.sourceforge.net/) offers.net interoperability. OminOrbPy (http://omniorb.sourceforge.net/) offers Python bindings. Et cetera.
If only CORBA had a C++ binding like ICE...
Sted
P.S.
Like many developers working with CORBA, I am grateful to Michi for his precious help within comp.object.corba in the early days.
Slashdot Mirror
> Objective C is getting garbage collection and properties. Properties? How do you know?
Actually it is difficult to find good alternatives to CORBA for high performance and/or mission critical distributed applications.
.net interoperability. OminOrbPy (http://omniorb.sourceforge.net/) offers Python bindings. Et cetera.
ICE, the middleware created by the company where the author of the article works, is very good.
The downsides:
- It is proprietary
- It is not free for commercial applications (this is not bad per se)
Most of the shortcomings of CORBA depicted by Michi Henning are true.
But some of them are avoidable.
These are some pros for CORBA:
- Many freeware implementations (TAO, OmniOrb, JacOrb, etc)
- Very good performances
- Good support (both from public forums and private companies - three or four companies, for instances, offer support for TAO)
- Interoperability with everything. Java is compatible out of the box (even if the JDK ORB is acceptable only on the client side). The excellent IIOP.NET (http://iiop-net.sourceforge.net/) offers
If only CORBA had a C++ binding like ICE...
Sted
P.S.
Like many developers working with CORBA, I am grateful to Michi for his precious help within comp.object.corba in the early days.
Was always the law predicting correctly or was the industry to try to follow its predictions?
Yes, this is sad. But they managed to get gcc 4.0 on board (with xcode 2). And gcc 4.0 is still in RC1.
I think than Mono is a good thing, but if I should start a server-side multi-platform project today, I would choose Java.