Re: Actually looking at the code - why init oafd
- From: Michael Meeks <michael ximian com>
- To: George <jirka 5z com>
- Cc: Maciej Stachowiak <mjs eazel com>, <gnome-2-0-list gnome org>
- Subject: Re: Actually looking at the code - why init oafd
- Date: Thu, 6 Sep 2001 22:55:06 -0400 (EDT)
Hi George,
On Thu, 30 Aug 2001, George wrote:
> oafd is NOT started on program init, gconfd is not started on program
> init. No CORBA calls are made.
AFAIR the oafd start on program init was an attempt to get round
issues with idle handlers and activation; inasmuch that liboaf does
something like:
user: do_some_oaf_call
liboaf: get_activation_server
fork_server
g_main_loop_iterate and listen to GIOChannel for IOR
user_idle: do_some_oaf_call
get_activation_server
fork_server ....
Which sucks. Clearly there are several possible solutions to this,
one of which I think was initializing oaf at app startup.
Perhaps this re-enterancy should be fixed inside bonobo-activation
by using either a custom mainloop there - or possibly the linc mainloop -
since then we can still get fun CORBA re-enterancy issues :-)
Regards,
Michael.
--
mmeeks gnu org <><, Pseudo Engineer, itinerant idiot
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]