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

List:       kde-core-devel
Subject:    Re: D-BUS required changes in KDE 4
From:       Matt Rogers <mattr () kde ! org>
Date:       2006-05-26 16:35:36
Message-ID: 200605261135.36207.mattr () kde ! org
[Download RAW message or body]

On Friday 26 May 2006 10:37, Thiago Macieira wrote:
> David Faure wrote:
> >On Friday 26 May 2006 11:35, Thiago Macieira wrote:
> >> David Faure wrote:
> >> >On Friday 26 May 2006 11:20, Thiago Macieira wrote:
> >> >> There are two things I have found out during my port of kdelibs to
> >> >> D-BUS that we will have to address:
> >> >>
> >> >> 1) Currently, the D-BUS session daemon isn't automatically started.
> >> >> This requires the user to have his scripts set up to start the
> >> >> daemon *before* any KDE application is started. For a KDE session,
> >> >> we can fix that with startkde, but imagine a user running KMail in
> >> >> TWM: KMail will refuse to start.
> >> >
> >> >We currently have code to start kdeinit (which starts dcopserver)
> >> > when a kde application doesn't manage to contact dcopserver (cf
> >> > KApplication::startKdeinit and KApplication::dcopFailure). Can't we
> >> > do exactly the same with DBUS?
> >>
> >> We could, but why not do it in the libdbus-1 library itself and let
> >> all programs using D-BUS to benefit from it?
> >
> >Sounds good.
>
> That does answer the question, though: is it a feature we should push for
> in D-BUS or should we simply mandate that the daemon be running in all
> circumstances?

the former. IMHO, this should be in DBUS.
--
Matt
[prev in list] [next in list] [prev in thread] [next in thread]