Feedback wanted: multiprocess KDED

[David Faure]

On Tuesday 25 March 2008, Sebastian Trüg wrote:
> > Are you going to move only specific services to sub-processes?
> 
> All of them.

This kills the purpose of KDED completely.
The idea of KDED is: instead of each little service being provided by a separate daemon,
having a single daemon with modules, one service per module. This minimizes the
number of "background processes" needed by KDE applications (think in particular
of people using one kde process in a non-kde environment, the number of daemons
we start is already too big for them).
This idea of (in-process) kded modules works well for simple things that are stable,
called upon only occasionally (otherwise your "problem 2" appears indeed)
(and ideally that don't show dialogs, especially not modal ones).
This fits well for things that simply store some kde-central data (ktimezoned, kpasswdserver, kwalletd...),
or that monitor something (networkstatus, kwrited, remotedirnotify...)

If it doesn't fit for some services (like nepomuk), then why does nepomuk use kded
in the first place instead of having its own daemon?

-- 
David Faure, faure at kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).