[Bug 46882] Make per-connection bus names non-mandatory

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=46882

--- Comment #3 from Simon McVittie <simon.mcvittie at collabora.co.uk> 2012-03-02 03:55:46 PST ---
(In reply to comment #2)
> In practice, object paths are now randomized too, right?

They correspond 1:1 to the bus names, so, yes.

> > at the moment the bus name acts as a mutex, preventing this.
> 
> Well, then it's an expensive socket-served mutex for purely local state, so it
> can hardly be the primary purpose.

Right, this is not their primary purpose, just making use of a side-effect; if
we lose the bus names, we'd have to find a different (probably purely local)
solution for object path uniqueness.

Another property provided by the bus names is that they guarantee that
connections' object paths are unique within the session (because uniqueness of
bus names is enforced by the dbus-daemon, and the object paths correspond 1:1
to bus names). This lets you refer to a connection by its object path only,
knowing that that's enough to refer to it uniquely and find its bus name (for
instance, Account.Connection relies on this).

To drop the Connection bus names we'd have to have another way to find the bus
name, probably by requiring that the Connection /o/fd/T/Connection/foo/bar/baz
owns the well-known name "o.fd.T.ConnectionManager.foo".

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA Contact for the bug.
You are the assignee for the bug.