Short lived, or "private", objects on the bus

Simon McVittie simon.mcvittie at collabora.co.uk
Fri May 18 04:30:35 PDT 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, 18 May 2007 at 12:55:09 +0200, Mikkel Kamstrup Erlandsen wrote:
> The problem is: If Search is and object on the bus, then what happens if
> another app decides to connect to the Search object? AFAIK there's no way to
> prevent this in dbus, but my knowledge here is pretty limited I must admit
> (hence my question on this list).

If you want to enforce the invariant that only one app calls methods on
each Search object, you can check the D-Bus message sender against the
calling app's unique name. D-Bus bindings should provide a way to get
the sender name (I hope they do, anyway, since a couple of methods in the
Telepathy D-Bus API are unimplementable on bindings that don't expose this
information).

Or, you can just document this requirement and say "don't do that".
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: OpenPGP key: http://www.pseudorandom.co.uk/2003/contact/ or pgp.net

iD8DBQFGTY5bWSc8zVUw7HYRAjs3AKDKqCf+QLE5KHVqsxJOw++xvaHiswCg4B3I
Rfs/AVW1Qrkg8iwnIL0TeL8=
=+hZF
-----END PGP SIGNATURE-----


More information about the dbus mailing list