Re: [Orbit-python-list] orb.run with threads

[Roland M. <ma...@ec...>]

Joseph T. Bore (2000-08-25 11:04:56 -0400) :

> Does this have something to do with the "global interpreter lock"
> that I've heard so much about?

I'm not enough of a CORBA guru to be able to answer that one :-)

> As I look at this further i've begun to wonder how you can write a
> gtk/corba(ORBit) application when I need to call gtk_mainloop and
> orb.run but yet neither of them returns until the program wants to
> go away.

  Yep.  This is probably not the answer you're expecting, but another
question instead: do you really need your Gtk application to be the
CORBA server?  What I personally do is that my CORBA server is a sort
of daemon, with very little user interaction (except for the command
line), and the monitoring application is another one, functioning as a
CORBA client.

> It seems that you would need to be multithreaded, but yet all of the
> evidence i've seen so fars indicates that python-orbit, and perhaps
> even orbit itself are not thread safe.

  Judging by the fact that there's a project to make ORBit
thread-safe, I think it currently isn't :-/

  What you *could* do, though, is the following.  Assuming you can have
a CORBA client in a thread (which might be a long reach, but only
testing will show me right or wrong), you could have a single-threaded
server storing the objects, and your multi-threaded thing would be a
CORBA client, changing the objects on the server so that other clients
could use them.  It's ugly, I know, yeah.  But the other way is to
contribute to the multithread-safe'ing of ORBit, so take your pick.

  In any case, I suggest you ask on the ORBit mailing list.  See the
page at <URL:http://mail.gnome.org/mailman/listinfo/orbit-list> for
more info.

Roland.
-- 
Roland Mas

Just a little bit of you every day will surely keep the doctors away.
  -- Just a little bit of you (The Jackson Five)