On Fri, 2005-12-02 at 11:33 +0000, Gustavo J. A. M. Carneiro wrote: > Sex, 2005-12-02 às 09:02 +0100, Jules Colding escreveu: > > On Thu, 2005-12-01 at 17:55 +0000, Gustavo J. A. M. Carneiro wrote: > > > Regarding http://bugzilla.gnome.org/show_bug.cgi?id=126477 > > > > > > I found this FAQ entry[1]: > > > > > > " *** How do I enable a threaded ORB ? > > > > > > Before you initialize the ORB ( or bonobo ) you need to call > > > linc_set_threaded (TRUE), this will cause all the locking to be setup > > > correctly. Calling this after locks have been created will not work." > > > > > > On the other hand, google found me an example[2] that contains this: > > > > > > (*orb) = CORBA_ORB_init(argc_ptr, argv, "orbit-local-mt-orb", ev); > > > > The ORB is forced into threaded I/O mode if the string "orbit-io-thread" > > is found anywhere in the ORB name. There is no checking for > > "orbit-local-mt-orb" anywhere in the source. > > Cool, thanks. So, is there any up-to-date ORBit2 threaded example?
Hmm.. I don't know. I am using a thread-aware ORB in my Brutus ORBit2 sample, but that might be too much just to see this option in action? Anyway, you can get it at www.omesc.com if you download the Brutus tarball. Look in "brutus/idl/samples/C". > Is requesting the "orbit-io-thread" ORB enough to make the ORBit2 core > thread safe? That should be it. Anything else is a bug. HTH, jules > I mean, regardless of any POA thread policies, I just need > to find out whether ORBit2 is in threaded mode, that's all. > > PS: I ask this because of > http://bugzilla.gnome.org/show_bug.cgi?id=126477 > _______________________________________________ orbit-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/orbit-list
