| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
the sink/source index with PA_INVALID_INDEX meaning unavailable
|
| |
|
|
|
|
| |
We put in the devices from the wire into a hashmap and then add all like type device in the database
and then order them based on priority (with the ones specified on the wire always being in that order at
the top of the list.
|
| |
|
|
| |
Also leave space for 'icon' and 'available' details too, althought currently this info is dummy.
|
| |
|
|
|
|
|
| |
The structure itself will contain various bits of info so exposing this fully to the client is a bad idea.
By keeping to a rename operation we keep what we do store abstracted from the clients.
Also fix some doxy comments.
|
| |
|
|
|
|
|
|
|
|
| |
This allows clients to edit the priroity order. What is not yet in place is the initialisation of that priority list
when new devices are detected or the cleaning (remove holes) when devices are removed.
In order to keep the storage transparent I will likely remove the write functionality and replace it with a
simple rename method.
I also still need to expose the priority itself when reading the data.
|
| |
|
|
|
|
|
| |
device-priority routing.
The routing logic itself does not yet exist, but the command currently will unload/load module-stream-restore as approriate.
(module-stream-restore would conflict with the role-based priority-routing).
|
|
|
This is effectively copied from the stream restore extension.
|
