Hi Luiz, > > This already fails today. Our code doesn't allow us to call twice the Connect > > method, so we can't have two of the same UUID connected. > > Well with RFCOMM you can't really connect multiple times to the same > channel/UUID and if we return the same fd clients will probably have > conflicts. you can not connect the same channel twice (except in the other direction), that is true, but you can connect to a different channel with a different UUID. That is the reason why we also allow connection by handles. Or at least we should. So even if we would make this limitation of 1 connection per UUID, the API is a fully asymmetric then. You are suppose to disconnect with the result of the connect call. I do not like that at all. It is bad API design and we are trying to squeeze this in the wrong way. Regards Marcel -- 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
