Re: starting/stopping components in bonobo-browser
- From: Michael Meeks <michael trna ximian com>
- To: Rodrigo Moya <rodrigo gnome-db org>
- Cc: GNOME Components <gnome-components-list gnome org>
- Subject: Re: starting/stopping components in bonobo-browser
- Date: Thu, 22 Nov 2001 00:59:22 -0500 (EST)
Hi Rodrigo,
On 21 Nov 2001, Rodrigo Moya wrote:
> Coverfire (dan coverfire com) is getting bonobo-support up to shape
> (after the initial port to GNOME 2 I did), and it would be great to
> be able to start/stop components from it, as was done in
> goad-browser.
>
> So, the question is how to do it with bonobo-activation.
Well - the thing is; why do you want to do that ? what
possible advantage can it give you to volentarily surrender resources
that are unused in order to fork a process, and register it with
bonobo-activation-server ?
Components should be demand activated;
> That is, is it useful to do so with bonobo components? and would it
> work to just call oaf_activate and oaf_deactivate on the components?
> Is it only useful to start/stop factories?
It doesn't sound that useful to me :-) However, it does sound
like you could screw load of apps up by de-registering a running
instance of a component server and thus forking a new one, creating
redundant processes and a confusing mess of servers.
One of the big things about oaf is that (theoreticaly) it does
the locking to ensure that you can be certain that only 1 server
process is activated.
Regards,
Michael.
--
mmeeks gnu org <><, Pseudo Engineer, itinerant idiot
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]