From oliver at littledevil.com.au  Sat Nov 25 23:53:37 2000
From: oliver at littledevil.com.au (Oliver George)
Date: Mon Feb  6 02:01:03 2006
Subject: [pyorbit] A non-blocking PyORBit question/suggestion...
Message-ID: <3A209751.7030600@littledevil.com.au>

Hello.

It seems pyORBit is dead now but it is part of debian stable so i'm 
loathed to give up just yet....

I have some comments/questions regarding the debian package python-orbit 
(aka. PyOrbit).  The python script call to orb.run() directly invokes 
CORBA_ORB_run(...) and as such doesn't return, this means that the 
python main
program loop is blocked.  This is fine for stand alone CORBA components 
but my intention is to add a CORBA interface on a server application.  I 
have a proposal for how to handle this situation.  Firstly when handling 
the call 'orb.run()' create a separate thread (in the corba module, not 
in python), invoke CORBA_ORB_run in this new thread.  Secondly, any 
interfacing invoked by the CORBA_ORB_run loop needs to resynchronise 
with the python interpreter before accessing the python objects.

I'm not a veteran of this stuff, but i'm pretty sure my suggestion is 
sound.  I tried to look into doing this myself.  I had troubles 
understanding where the accesses of the python objects occur.

Any suggestions would be appreciated,

regards Oliver George.