[omniORB] omniORB thread creation

[Kevin Wooten]

Unfortunatly we do. We are using COM ( again, UNFORTUNATLY ) which =
requires calls to CoInitialize, and CoUninitialize. Are current solution =
is to call these functions as needed during a method invocation. This is =
causing problems, one, objects that are marshalled across threads in COM =
seem to get disposed of. Two, it slows everything down. What we need is =
to initialize on thread create, and uninitialize on destruction. How =
hard would it be to add this wrapper back, since I am developing with =
omniORB4 (for the wide strings)? Maybe I can help??

>> -----Original Message-----
>> From: Duncan Grisby [mailto:dgrisby@uk.research.att.com]
>> Sent: Monday, March 18, 2002 4:38 AM
>> To: Kevin Wooten
>> Cc: omniorb-list@uk.research.att.com
>> Subject: Re: [omniORB] omniORB thread creation=20
>>=20
>>=20
>> On Wednesday 13 March, "Kevin Wooten" wrote:
>>=20
>> > Is there any way to run some startup code whenever a thread is
>> > created by omniORB? Specifically we need to initialize COM so our
>> > SQLServer database driver works.
>>=20
>> See giopServerThreadWrapper in include/omniORB3/omniORB.h.
>>=20
>> Do you _really_ have to do that?  The wrapper is no longer used in
>> omniORB 4. Perhaps I should put it back...
>>=20
>> Cheers,
>>=20
>> Duncan.
>>=20
>> --=20
>>  -- Duncan Grisby  \  Research Engineer  --
>>   -- AT&T Laboratories Cambridge          --
>>    -- http://www.uk.research.att.com/~dpg1 --
>>=20