Re: [Orbit-python-list] orb.run with threads
Status: Inactive
Brought to you by:
tack
From: Jason T. <ta...@li...> - 2000-08-25 17:13:48
|
> Now here is where my naivete comes in about extending the python > interpreter. Is it possible to have pyorbit release the lock right I don't know about pyorbit, but I'm sure it's possible with ORBit-Python. :) (PyOrbit is a different project.) > before it blocks and then after it unblocks, re-aquire the lock? It > just cant be that simple I'm sure. As I understand it, this is pretty much how it must work. However, with the sort of arrangement in ORBit-Python it might not be so clear cut. On the server side, you'll need to release the lock before calling CORBA_ORB_run(). Then in operation_skel, reclaim the lock and release it after exiting. On the client side, you'd release the lock before invoking any of the GIOP calls (which can potentially block for a long time if over a slow connection), and then reacquire it after. Feel free to give this a whirl and let me know how it goes. > I'd be willing to help out with this, but I'm going to probably need > some help figuring out some of the internals that I dont know already. If you have any questions, by all means ask on the list. I'm sure either myself or Roland (or someone else in the know) will get back to you. > if all goes well i'd help out there too. Glad to hear it! Cheers, Jason. |