[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-core-devel
Subject: Re: KDED Modules and their DBus Path
From: Thiago Macieira <thiago () kde ! org>
Date: 2008-04-22 21:37:22
Message-ID: 200804222337.22382.thiago () kde ! org
[Download RAW message or body]
Michael Jansen wrote:
>> One reason for the org.kde.kded /modules/<modulename> naming is that
>> it allows the autoload feature of kded to work (just make a call to a
>> module and it will be loaded if necessary).
>
>That i didn't knew. But that is only of interest for autoload enabled
> modules. And again. I don't like that we expose a implementation detail
> for this purpose.
It's not. I chose the name "/modules/<modulename>" because I liked that
better than "/<modulename>". That's the only reason why they are there
right now.
The autoloading feature could be implemented with any path scheme. It just
has to be deterministic: we have to be able to extract the module name
from *somewhere*.
>A method like 'gimme service xyz, however that is implemented' would be
> my preferred solution. Is it possible to register a standalone daemon
> under /modules/<modulename> ?
No.
But you can register an auto-startable service with D-Bus. If it's part of
kded, kded will have to register it when it starts. If it's standalone,
then D-Bus will launch the application when any application tries to use
it.
It can even be both.
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
["signature.asc" (application/pgp-signature)]
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic