session-manager: split policy and monitor

Separate the session manager in a monitor and policy part.

The monitor manages the devices and endpoints.

The policy watches the nodes/ports/clients and applies the policy
of linking them.

Because both now have a separate connection, we can remove some
hacks in the protocol. When a remote was both the implementer and
user of an object we could get in a deadlock when the user was
blocked waiting and the implementator was blocked sending a reply.
We used to un-busy a client when it was expecting a reply from a
ping or sync for this reason.

Add and use some more keys for the endpoints and streams.
This commit is contained in:
Wim Taymans 2019-11-07 16:03:00 +01:00
parent 8bbfe876a7
commit 4ad7ce3aa2
11 changed files with 138 additions and 1365 deletions

View file

@ -1007,7 +1007,7 @@ int pipewire__module_init(struct pw_module *module, const char *args)
pw_protocol_native_init(this);
pw_protocol_native0_init(this);
pw_log_debug(NAME" %p: new %d", this, debug_messages);
pw_log_debug(NAME" %p: new debug:%d", this, debug_messages);
d = pw_protocol_get_user_data(this);
d->protocol = this;