Xpra: Ticket #2349: cache gstreamer config

Related to #2341 and #2347. Similar to #2345.

Instead of running xpra _sound_query every time we run the client or server, we could cache the results in a text file and just reload it.

We would need to ensure that the timestamp on this file is newer than the gstreamer plugins directory, so that we query it again whenever plugins are added or removed. This is similar to what gstreamer does with its plugin registry (now found in .cache/gstreamer-1.0/) - can we re-use this mechanism without incurring the same startup cost?

Mon, 22 Jul 2019 14:43:38 GMT - Antoine Martin: attachment set

cache sound query data

Mon, 22 Jul 2019 14:46:09 GMT - Antoine Martin: status changed; resolution set

The patch above implements sound query caching, but there are problems:

So, I don't think we should be doing this..

Sat, 23 Jan 2021 05:48:55 GMT - migration script:

this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/2349