On Sun, 2013-11-24 at 08:48 +0200, Tanu Kaskinen wrote: > Who manages and owns the connections? If there's no router, the core > will of course need to manage the connections. The natural owner for > sink input connections in this case is pa_sink_input. If there is a > router, then connections may be created by the router, and I think it > makes sense in that case to make the router also the owner of the > connections, so freeing the connections is then also the responsibility > of the router. Hopefully it won't become too complex to tell apart > connections owned by the core and connections owned by a router. Arguing with myself... It starts to feel like a better idea to not have any specific owner for connections (or formally pa_core could be the owner). If a router sets up a bunch of connections and then the router module is unloaded, those connections shouldn't be removed, and I don't want to play any ownership transfer games either. Hmm, actually, once I add routing domains to the system, then the routing domain will be the right place to store the connections. When a domain is removed, all connections in that domain should be removed too. Until domains are added, however, pa_core shall be the place for holding the connections. -- Tanu
