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

List:       kfm-devel
Subject:    Re: kded problems
From:       weis () stud ! uni-frankfurt ! de
Date:       1999-06-07 9:17:03
[Download RAW message or body]

Hi,

On Fri, 4 Jun 1999, Simon Hausmann wrote:

> On Fri, 4 Jun 1999, David Faure wrote:
> 
> > On Fri, Jun 04, 1999 at 01:03:38AM +0200, Simon Hausmann wrote:
> > > But perhaps I'm missing another possibility.
> > > Does anyone have an idea?
> > Yes, you :)  Below.
> > 
> > I think your idea is 100% right.
> > You have my vote :)
> 
> Hehe, ok :)
>  
> > However, does it solve the "konqueror-should-IMHO-register-to-kded-on-startup" problem ?
> > It doesn't seem so....
> > 
> > > > > As a workaround to this we could make konqueror bind its application
> > > > > object (which is usually loaded by the autoloader otherwise) to a fixed
> > > > > name in the naming service. But of course only if this hasn't been done by
> > > > > another instance already.
> > > > Yup.
> > > > 
> > > > > Now we could make kfmclient look up in the naming service for konqy and
> > > > > use it instead of asking kactivator to possibly start a new service.
> > > > Why "instead of" ? Can't we simply make the activator use konqueror's registration ?
> > > 
> > > Which registration? ;-)
> > > The problem is that only a konqueror process which got started from the
> > > mediators is able to register itself as running server. At least I see no
> > > other way.
> > I don't see why.
> > The kded IOR is on the root properties, so konqueror can connect to it
> > some way, right ? (I mean konqueror can ask libkded to connect to it)
> 
> Yesyes, konqueror can always "connect" to kded, that's no problem.
> BUT: How can we tell the mediators about being a running server (about
> being an implementation) ?
> 
> Perhaps it is possible, which would solve the problem then, but I'm
> 100% clueless how to do it. Perhaps others (Steffen, Torben?) can help?

Sorry, I did not follow this thread.

Bye
Torben

> And as workaround for this I thought of letting the server register itself
> at a little naming service, if it has not been started by the mediators
> anyway. This should solve your above mentioned "konqueror-should-IMHO-register-
> to-kded-on-startup" problem, or? :-)
> 
> 
> Ciao,
>   Simon
> 
> --
> Simon Hausmann       <hausmann@kde.org>
> http://www.kde.org/  <tronical@gmx.net>
> 
> 
> 

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