[pulseaudio-discuss] [RFC] Exposing ports and profiles to clients

[David Henningsson]

Two different proposals (very drafty) on how to expose ports for 
inactive profiles, dunno which one is better. The first one adds a 
cross-reference struct which will repeat itself for every combination of 
port and profile. The second one adds a profile list for every port. The 
second one looks less ugly, but would bloat the network a little more as 
that would make pa_sink_port_info include the profile list as well.

Both proposals add port lists to the card. The internal structure for 
this is coming soon to a patch near you.

Both patches can also be combined with a patch that would merge 
pa_source_port_info and pa_sink_port_info into a single struct (for 
simplicity).

Note: as some of you might remember, I tried adding a "ports" field to 
the pa_card_profile struct, but that broke the ABI as pa_card has a list 
that's depending on the size of pa_card_profile.

// David
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 1_crossref.diff
Type: text/x-patch
Size: 1075 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/pulseaudio-discuss/attachments/20111023/66ce1acd/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2_port_has_profile_list.diff
Type: text/x-patch
Size: 1700 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/pulseaudio-discuss/attachments/20111023/66ce1acd/attachment-0001.bin>