[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gnome-components
Subject:    Re: starting/stopping components in bonobo-browser
From:       Rodrigo Moya <rodrigo () gnome-db ! org>
Date:       2001-11-22 12:19:53
[Download RAW message or body]

On Thu, 2001-11-22 at 06:59, Michael Meeks wrote:
> 
> 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.
> 
ok, so it makes no sense to do it. That's what I was thinking, but as
goad-browser did it, we were thinking on having the same functionality.

cheers
-- 
Rodrigo Moya <rodrigo@gnome-db.org> - <rodrigo@ximian.com>
http://www.gnome-db.org/ - http://www.ximian.com/
_______________________________________________
gnome-components-list mailing list
gnome-components-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-components-list

[prev in list] [next in list] [prev in thread] [next in thread]