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

List:       kde-core-devel
Subject:    Re: DCOP bug again :} (Re: Password caching for io-slaves)
From:       Dawit Alemayehu <adawit () starpower ! net>
Date:       2000-05-18 14:23:41
[Download RAW message or body]

On Thu, 18 May 2000, David Faure wrote:
> On Thu, May 18, 2000 at 10:02:17AM -0400, Dawit Alemayehu wrote:
> > On Wed, 17 May 2000, David Faure wrote:
> > > On Wed, May 17, 2000 at 03:16:36PM -0700, Waldo Bastian wrote:
> > > > On Wed, 17 May 2000, David Faure wrote:
> > > > > > > Hmm, ok, so we're back to a bug in DCOP, which doesn't handle properly
> > > > > > > requests made right after a program is started.
> > > > > >
> > > > > > Does process() gets called in the kio_uiserver? Can you check whether a
> > > > > > reentrant call to process() occurs?
> > > > >
> > > > > DCOP: register 'kio_uiserver'
> > > > > DCOP: register 'anonymous-3287'
> > > > > normal call to process!
> > > > > kio (UIServer): User dfaureHeader dfaure@localhostKey localhost
> > > > > kio (UIServer): Checking if password is cached for localhost
> > > > > kio (UIServer): No running kdesu daemon found. Starting one...
> > > > ^^^^^^^^^^^
> > > > 
> > > > You do a dcopcall from within process()... I think that confuses DCOP. I had 
> > > > the same problem within KLauncher where I called isApplicationRegistered() 
> > > > from within process(). 
> > > 
> > > Ah. That's what happens when we start using DCOP extensively...
> > > This shows a flaw in the current design, then.
> > > Dawit, if the passwd cache is done in kdesud, why not let the observer
> > > query kdesud directlry first, and if a dialog box needs to be
> > > shown, THEN call uiserver's method (renamed to openPassDlg) ?
> > > That sounds like the right thing to do IMHO.
> > 
> > Should I rever this back to my original design ?  None of the DCOP problems
> > will be present, but we will be definitely have the dependncy issue.  David, 
> > if I do it the way you suggest here, it seems to me that the dependency would
> > still be there.
> 
> Yes... I thought you could talk to kdesud directly, using DCOP,
> but appareently it's not the case.
> (you need the 'kdesuclient', in case the server is not running
> or not allowed to run, etc.).
> Don't revert anything yet, Waldo has the solution for those DCOP problems ;-)

Okay, great.  Moving on to other things...

Regards,
Dawit A.

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