[Portland] Current plan summarized

[Lubos Lunak]

On Wednesday 15 March 2006 17:46, Dan Kegel wrote:
> On 3/15/06, Kevin Krammer <kevin.krammer at gmx.at> wrote:
> > Current DAPI approach
> >
> > application --marshalled API call--> DAPI daemon (service implementation)
> >
> > Your suggestion:
> >
> > application -- marshalled API call --> DBus  -- marshalled API call -->
> > service implementation
> >
> > Using DBus as the transport actually has one daemon more, the
> > DBus-Daemon.
>
> If I recall properly, all new linux distros are going to have a DBus daemon
> running anyway.  The system I'm running right now (Ubuntu 05.10) does.
>
> > In both cases DEs can do the service implementation in an extra process,
> > but don't have to, e.g. KDE could implement it as another kded module
> > (i.e. plugin; kded is the KDE service daemon which is always present in
> > KDE sessions)
>
> Ah, I see, we're having a "should kde switch to dbus" argument without
> realizing it.

 No, it's only about you mixing two different daemons. See the two diagrams 
above.

-- 
Lubos Lunak
KDE developer
---------------------------------------------------------------------
SuSE CR, s.r.o.  e-mail: l.lunak at suse.cz , l.lunak at kde.org
Drahobejlova 27  tel: +420 2 9654 2373
190 00 Praha 9   fax: +420 2 9654 2374
Czech Republic   http://www.suse.cz/