[omniORB] Single-Threading POA Policy

[vonWedel@lfpt.rwth-aachen.de]

Dies ist eine mehrteilige Nachricht im MIME-Format.
--=_alternative 004BBB65C1256981_=
Content-Type: text/plain; charset="us-ascii"

Hello,

I'm using omniORBpy (1.2) to wrap some COM object, making its 
functionality
available in the CORBA world.

The problem I have is that, using PythonWin, a COM object reference 
marshalled
in one thread cannot be used for calls in another.

Unfortunately, exceuting subsequent calls in distinct threads is the way 
omniORB handles
things, even when configuring a new POA to do single threading.

Is there any way to circumvent this?

Of course, I can build some sort of (thread-safe) event queue to which the 
CORBA
calls write and from which an additional COM handler reads (the latter 
running in a
single thread on its own), but this seems to be quite a  bit of 
unnecessary work...

Any better ideas?

Lars

--=_alternative 004BBB65C1256981_=
Content-Type: text/html; charset="us-ascii"




<br><font size=2 face="sans-serif">Hello,</font>
<br>
<br><font size=2 face="sans-serif">I'm using omniORBpy (1.2) to wrap some COM object, making its functionality</font>
<br><font size=2 face="sans-serif">available in the CORBA world.</font>
<br>
<br><font size=2 face="sans-serif">The problem I have is that, using PythonWin, a COM object reference marshalled</font>
<br><font size=2 face="sans-serif">in one thread cannot be used for calls in another.</font>
<br>
<br><font size=2 face="sans-serif">Unfortunately, exceuting subsequent calls in distinct threads is the way omniORB handles</font>
<br><font size=2 face="sans-serif">things, even when configuring a new POA to do single threading.</font>
<br>
<br><font size=2 face="sans-serif">Is there any way to circumvent this?</font>
<br>
<br><font size=2 face="sans-serif">Of course, I can build some sort of (thread-safe) event queue to which the CORBA</font>
<br><font size=2 face="sans-serif">calls write and from which an additional COM handler reads (the latter running in a</font>
<br><font size=2 face="sans-serif">single thread on its own), but this seems to be quite a &nbsp;bit of unnecessary work...</font>
<br>
<br><font size=2 face="sans-serif">Any better ideas?</font>
<br>
<br><font size=2 face="sans-serif">Lars</font>
<br>
--=_alternative 004BBB65C1256981_=--