[omniORB] Two orbs in the same process

[Kevin Wooten]

I believe somewhere the spec. says that the third string you pass to =
CORBA::ORB_init is supposed to identify the ORB. Meaning that calling =
ORB_init twice with two different identifiers should yield two seperate =
ORB's, on the reverse calling ORB_init twice with the same identifier =
will yield the same ORB from both calls. Now for the rub, omniORB =
requires the identifier to be "omniORB<VERSION>" (e.g. "omniORB3"). This =
leads me to believe "no can do" for omniORB, unless every call to =
ORB_init creates a completely new ORB.

HTH,
Kevin

>> -----Original Message-----
>> From: Attila Pletyak [mailto:attila.pletyak@anemo.com]
>> Sent: Wednesday, February 27, 2002 1:38 PM
>> To: omniorb-list@uk.research.att.com
>> Subject: [omniORB] Two orbs in the same process
>>=20
>>=20
>> Is it possible to create two different ORBs in the same process, both
>> having their own clientCallTimeout set differently?
>>=20
>> I need a solution where the incoming requests should be=20
>> served out fast,
>> but if it cannot happen (because of heavy load) I assume some default
>> setting and put the request in a background process which=20
>> can wait then
>> longer.
>>=20
>> I've dreamed of a solution where I create a new thread in my original
>> process having a different ORB for communication, and=20
>> therefore, having
>> a different client call timeout period.
>>=20
>> TIA,
>>=20
>> Attila Pletyak
>> Anemo Ltd.
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20