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

List:       kde-core-devel
Subject:    KSharedConfig inter-process change notification?
From:       Andriy Rysin <arysin () gmail ! com>
Date:       2010-02-14 4:16:51
Message-ID: 3e02eb611002132016g29e52b2cl355f04bd9d9f6c59 () mail ! gmail ! com
[Download RAW message or body]

Hi all

I am currently rewriting kxkb into kded daemon, plasma applet and a reusable
widget and have a question on config change notification. Seems like usually
we have to send dbus message. But if I have several components (kded daemon,
plasmoid etc) which need to know about config change made in KCModule it'll
will have to know about all of them to send the message out.

Seems like the nicer way would be to allow interested parties to connect to
some signal (e.g. "configChanged") in KSharedConfig and when sync is made
send this signal out. Different engines could be used for that: internal KDE
IPC messaging or even fam. Then the module which changes config should not
care of the consumers and consumers would not have to expose "reloadConfig"
or "restart" method.

Is there something around or sending the dbus message from the modifier is
the only way?

Thanks,
Andriy

[Attachment #3 (text/html)]

Hi all<br><br>I am currently rewriting kxkb into kded daemon, plasma applet=
 and a reusable widget and have a question on config change notification. S=
eems like usually we have to send dbus message. But if I have several compo=
nents (kded daemon, plasmoid etc) which need to know about config change ma=
de in KCModule it&#39;ll will have to know about all of them to send the me=
ssage out.<br>
<br>Seems like the nicer way would be to allow interested parties to connec=
t to some signal (e.g. &quot;configChanged&quot;) in KSharedConfig and when=
 sync is made send this signal out. Different engines could be used for tha=
t: internal KDE IPC messaging or even fam. Then the module which changes co=
nfig should not care of the consumers and consumers would not have to expos=
e &quot;reloadConfig&quot; or &quot;restart&quot; method.<br>
<br>Is there something around or sending the dbus message from the modifier=
 is the only way?<br><br>Thanks,<br>Andriy<br><br>


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