Short lived, or "private", objects on the bus
Mikkel Kamstrup Erlandsen
mikkel.kamstrup at gmail.com
Fri May 18 05:44:02 PDT 2007
2007/5/18, Simon McVittie <simon.mcvittie at collabora.co.uk>:
> -----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
> > (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
Yes, this could work, but it appears to me that it is a hack just as much as
using handles instead of objects is a hack... No?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the dbus