new kde project
gav at kde.org
Fri Jun 6 11:44:53 BST 2003
On Friday 06 June 2003 03:39, Ian Reinhart Geiser wrote:
> On Thursday 05 June 2003 08:19 pm, Gav Wood wrote:
> > since it's a kded service, to restart it all you have to do is go into
> > kcontrol and under service manager select the lirc entry and press the
> > stop button, followed by the start button.
> Please reconsider the poor design choice of a kded module for the following
> any deadlocks or hangs in your code will end anyones kde fun quickly
> any crashes in your module will likewise cause pain dejour
> dcopservices are easier to manage (start/stop/kill -9 when they go nuts
> and eat cpu and memory)
> any memory issues go away on the dcopservices restart vs kded modules
what you say is true, but likewise if all developers heeded these warnings or
thought they had any real bearing on the choice of design then there would be
no kded shared library modules at all.
in fact, there are many kded modules in shared library form, so clearly there
must be some consensus that for a simple "daemon-like" extension a kded
module is a good design choice, no?
in addition to this i would imagine that the code is so straightforward that
it's probably possible (with the help of a few assertions and guards) to
_prove_ that it will not crash or hang.
what exactly are kded modules supposed to be for anyway?
Gav Wood <gav at kde.org>
codito ergo non satis bibivi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
More information about the kde-core-devel