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

List:       kfm-devel
Subject:    Fwd: Re: kdebase/konqueror/client
From:       David Faure <david.faure () insa-lyon ! fr>
Date:       1999-06-06 19:34:40
[Download RAW message or body]

Moving to kfm-devel as well ;)

----- Forwarded message from David Faure <david.faure@insa-lyon.fr> -----

Date: 	Sun, 6 Jun 1999 21:25:18 +0200
From: David Faure <david.faure@insa-lyon.fr>
To: kde-cvs@max.tat.physik.uni-tuebingen.de
Cc: Steffen Hansen <stefh@mip.sdu.dk>
Subject: Re: kdebase/konqueror/client

On Sun, Jun 06, 1999 at 09:15:37PM +0200, Simon Hausmann wrote:
> 
> On Sun, 6 Jun 1999, David Faure wrote:
> 
> > [...] kded doesn't know about the running kdesktop.
> > 
> > Simon, is there a plan about this finally ?
> > How does kded know about running applications / servers ?
> > 
> > Your last posts on kfm-devel suggest a small naming service (a QMap).
> > and I guess a method somewhere in libkded to register the existing CORBA 
> > objects to this service. I think that's a good solution.
> > And it wouldn't require libkom for simple apps like kdesktop.
> > Just registering the interface name ("IDL:K...:1.0") and the object ptr.
> 
> Well, yes, I had the random thought of doing some tricks with KActivator
> and KNaming (make kact look in the naming service for a running server,
> etc.) , but I dropped this. IMHO this doesn't really make things more
> comfortable but rather more complicated (also to implement) .
> 
> IMHO the safest and most solid way is to keep the naming service
> completely independend from things like kactivator.
Sure, since kactivator launches new apps whereas we want
to connect to running ones....

Well, it means in fact that the naming service, if asked for
a non-running server, would still use the activator to launch it,
right ?
So it's not 100% independent...

> The resulting steps for kfmclient (client) and kdesktop (as server) would
> look like:
> KDesktop registers itself at KNaming at startup.
> Kfmclient finds it there and uses it.
Simple ;)

> What do you think?
Not sure about which tricks you are talking about above,
but a simple registration and binding mechanism is fine with me.

-- 
David FAURE
david.faure@insa-lyon.fr, faure@kde.org
http://www.insa-lyon.fr/People/AEDI/dfaure/index.html 
KDE, Making The Future of Computing Available Today

----- End forwarded message -----

-- 
David FAURE
david.faure@insa-lyon.fr, faure@kde.org
http://www.insa-lyon.fr/People/AEDI/dfaure/index.html 
KDE, Making The Future of Computing Available Today

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