2007/5/18, Simon McVittie <<a href="mailto:simon.mcvittie@collabora.co.uk">simon.mcvittie@collabora.co.uk</a>>:<div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> -----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).</blockquote><div> 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? Cheers, Mikkel </div> </div>