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

[bugzilla-daemon at freedesktop.org]

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

--- Comment #2 from Mikhail Zabaluev <mikhail.zabaluev at nokia.com> 2012-03-02 03:36:37 PST ---
(In reply to comment #1)
> The original rationale for this was that it supports CMs implemented using a
> library that can only make one connection per process. On RequestConnection,
> such a CM could take a bus name for its Connection (perhaps with its process ID
> in the name), then drop its ConnectionManager name.

I suspected something like that. But that either presents a race condition, or
requires all clients to gracefully handle a "can't do it now, try again later"
error for RequestConnection. So this doesn't seem like it can work reliably
with current client software.

> There's nothing to stop someone implementing
> 
>     <allow own_prefix="org.freedesktop.Telepathy.Connection.gabble"/>
> 
> as something the policy language can do. With my D-Bus maintainer hat on, I
> think that'd be a better way to represent this than supporting shell-style glob
> patterns.

That would be great, and perhaps bring more good to the universe than tweaking
Telepathy would do.

> TpBaseConnectionManager would have to keep a global registry of Connections by
> object path (or use more modern libdbus API, try_register), to avoid trying to
> register two connections at the same object path and crashing itself;

In practice, object paths are now randomized too, right?

> 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.

-- 
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.