In the case of HDP, the same device may support two different roles (source and sink) on a single SDP record. For example, a data concentrator that collects data from sensors and forwards to a PC will have a number of source and sink MDEPs, all of them under a single SDP record and a single "listening" L2CAP socket for MCAP control channel. When a remoty party connects, only the data channels that match are connected (both of same data type, one side source, other side sink). That's why we chose a single interface, a generic RegisterRole(), and role appears again in EndPoint dict. > In case of MDEP we might want to have two interfaces > org.bluez.HealthSink and org.bluez.HealthSource, this should fix the > reusing the interface name with different methods in adapter path and > device path, internally the code can take care of matching local ones > with remotes ones, well at least we did that for a2dp sink/source > although it is a completely different profile I think it might be > useful to have a similar logic in this case otherwise the ui (if there > is any in this case) has to figure out a lot of details to connect, > again in a2dp there is also sink/source concept and support for > multiples remote/local seps but we try to hide as much as possible in > the API. > > -- > Luiz Augusto von Dentz > Computer Engineer -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
