[omniORB] COM-omniORB Interface

[David Morgenlender]

Eric,

>I agree with you about pricing, particularly when compared to the
>bundled CORBA support I believe is now in JBuilder. However, I was only
>suggesting VisiBroker as a possibility for your client end, not
>necesarily for the server app, which could still use OmniOrb. Using 2
>different CORBA 2 compliant orbs *shouldn't* be a problem, but still...

That's still a possibility, although unlikely ...

>In any event, I would be very interested in knowing how you get on with
>your BCB 3.0/OmniOrb integration.

At this point, the integration is on hold, possibly permanently.  Since I=
 must
implement a COM interface, there's no reason the BCB app cannot use it!
Therefore, there would be no need to implement the CORBA client =
capability.

The big issue is whether any 3rd party COM-CORBA bridge supports my =
environment
...  omniORB server on one system (ETS-Kernel) & COM client on another =
system
(Win95 or NT), with ALL of the bridge going on the client system.

Meanwhile, I'm trying to get omniORB running under ETS-Kernel.  So far =
I've got
it building ok & I'm trying to handle its need for a configuration file =
&/or
registry for configuration information.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
Dave Morgenlender
e-mail: dmorgen@alum.mit.edu
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D