[pulseaudio-discuss] [PATCH v0 1/2] reserve: Add support for private D-Bus connections

Mikel Astiz mikel.astiz.oss at gmail.com
Tue Jan 29 01:26:32 PST 2013

Hi David,

On Tue, Jan 29, 2013 at 8:10 AM, David Henningsson
<david.henningsson at canonical.com> wrote:
> On 01/28/2013 05:59 PM, Mikel Astiz wrote:
>> From: Mikel Astiz <mikel.astiz at bmw-carit.de>
>> Extend the reserve-monitor API with a registration mechanism to keep
>> track of existing private connections. This is necessary because the
>> monitor should not consider it busy if a device has been owned by us.
> Am I missing an earlier thread here, or why do we need this? Isn't the
> existing checks (that I pushed to 3.0 stable) enough to give a correct
> "busy" result?

The "busy" result is working fine except if private D-Bus connections
are used, as introduced in patch v0 2/2.

In this case the unique name of the bus differs compared to the bus
used by the monitor, but we still want to consider it as non-busy.

I'll make this more clear in the header-file comment in v1, as
suggested by Tanu.


More information about the pulseaudio-discuss mailing list