George Kiagiadakis 444d180218 session-manager: endpoint: implement caching info & params ... The info structure needs to be cached because there is no way to request it from the implementation, unless we hack the add_listener API to be used for making info requests or add a new method that will be used just in the implementation (both are bad ideas). The params are cached because 1) a client doing enum_params + sync will not work correctly, since the sync call syncs with the server and not the implementation... we could block the client to solve that, but then there is also #2 2) the implementation is not aware of the clients and therefore it cannot keep track of who is subscribed and who is not, this needs to happen in the server. Then if we only keep track of the subscriptions in the server and keep requesting params from the impl, there is no way to know if a param event coming from the impl matches a call to enum_params or to subscribe or if it's just an update that needs to be forwarded to subscribers.		2020-03-27 14:56:07 +00:00
..
daemon	conf: update defaults	2020-03-18 17:53:46 +01:00
examples	examples: small improvements	2020-03-20 11:24:29 +01:00
extensions	session-manager: add update/free functions for the info structures	2020-03-27 14:56:07 +00:00
gst	pipewireclock: use the monotonic time for now	2020-02-11 13:08:04 +01:00
modules	session-manager: endpoint: implement caching info & params	2020-03-27 14:56:07 +00:00
pipewire	context: allow quantum up to configured max	2020-03-26 11:27:36 +01:00
tests	device: implement subscribe_params	2020-02-12 16:07:10 +01:00
tools	pw-cat: allow latency=none	2020-03-26 11:34:59 +01:00
.gitignore	move things around	2017-07-11 16:08:22 +02:00
meson.build	meson: add tests option	2020-02-23 00:09:16 +01:00