On Mon, 26 Apr 1999, The Hermit Hacker wrote:
> I use KDE at home, as well as at work...KDE uses MICO...
>
> The CORBA implemetaion, as discussed before, is going to have to be
> 'wrappered' so that it isn't tied to any particular implementation...
The language bindings for CORBA are completely standardized. The only
thing you have to change are your header files and link options.
That said, the CORBA C bindings are different from the CORBA C++ bindings,
and so you are going to have to chose which language to pursue. I suggest
that staying with C is the natural choice for PostgreSQL, and you have
two very good free ORBs to chose from: ORBit and ILU. For C++, you
have one more real choice: OmniORB, MICO, and TAO. The two performance
champs are ORBit and TAO, which fortunately enough covers both of your
language choices. The language issue weighs heavily in my mind as a C
programmer who doesn't want to play the popular-subset- of-the-month
game with C++. (I think it's templates this month, although virtual
somethings are making a comeback. But don't use multiple inheritance!
That was all the rage back in '95, but now only dorks use it!)
Plus, if you code the Postgres part with ORBit, there's no reason why
clients can't use MICO; that's the whole point.
> Taral was, I believe, planning on starting with MICO and then let's those
> using other implementations build up from there...
Is all of the underlying glue work going to be done in C++?
--
Todd Graham Lewis Postmaster, MindSpring Enterprises
tlewis@mindspring.net (800) 719-4664, x22804
"A pint of sweat will save a gallon of blood." -- George S. Patton
