From kde-core-devel Thu Jul 13 13:43:42 2006 From: Thomas Zander Date: Thu, 13 Jul 2006 13:43:42 +0000 To: kde-core-devel Subject: Re: DBus/QtDBus Concerns Message-Id: <200607131543.43222.zander () kde ! org> X-MARC-Message: https://marc.info/?l=kde-core-devel&m=115279831227953 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--nextPart12534615.2E4KB0lUNS" --nextPart12534615.2E4KB0lUNS Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thursday 13 July 2006 12:55, David Jarvie wrote: > On Thursday 13 Jul 2006 10:31, Thomas Zander wrote: > >On Thursday 13 July 2006 01:50, David Jarvie wrote: > >> KAlarm and kalarmd need to interact via D-Bus. If some other > >> application made certain D-Bus calls, alarms could be lost. > > > >Only if those applications were malicious. If you expect things to get > >lost due to bugs, I suggest you take a long look at the interaction > > you have via dbus since that may need some work ;) > > I'm thinking more in terms of people trying to do clever things with > the "private" interface, which might mess things up. Bugs have to be fixed; this has nothing to do with the transport medium. Its like Windows saying it will only send emails to other Windows boxes=20 since others might loose it. I won't even comment on how wrong that is. > >What you are suggesting is to close the alarms modification to one > > client only. I think this is fundamentally the wrong path to walk > > down. =2E.. > The alarm daemon never adds, deletes or modifies alarms. Only KAlarm > can do this, and it has public D-Bus functions for this purpose.=20 So, you really are suggesting that nobody can create a KAlarm replacement=20 that talks to the KAlarm daemon via dbus? =2D-=20 Thomas Zander --nextPart12534615.2E4KB0lUNS Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQBEtk4PCojCW6H2z/QRAiESAJ9Mlgv8j1HoU1hOTJ0or5yS1p8jTQCfeEIg 3jaTY80iqDTG/1tpoB/t1Y8= =f5Q8 -----END PGP SIGNATURE----- --nextPart12534615.2E4KB0lUNS--