[pulseaudio-discuss] [PATCH 3/3] zeroconf: Make Avahi usage in m-z-publish async

[David Henningsson]

On 05/15/2013 06:43 AM, Arun Raghavan wrote:
> This pushes all avahi-client code to a threaded mainloop from the PA
> mainloop context. We need to do this because avahi-client makes blocking
> D-Bus calls, and we don't want to block the mainloop for that long.

Thanks for working on this, but I wonder whether there is actually a use 
case for having it blocking too?

E g, if you want a login sound and you want it played on the avahi 
discovered sink instead of the local one, that will now be impossible, 
because that sink is not discovered yet.

Also, is there a recent Avahi change that would cause this regression or 
has it always been there? I've never heard of this 20 s delay before.

> The only exception to this now that I don't see a workaround for is
> during module unload time. However, this shouldn't be a huge problem
> since in most cases, this will only happen at server shutdown time.
>
> The bulk of the change is partitioning the data so that PA core objects
> only (well, moslty) get accessed in the PA mainloop and Avahi calls

s/moslty/mostly



-- 
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic