Hi Marcel, Gustavo, On Tue, Aug 23, 2011 at 7:45 PM, Gustavo Padovan <padovan@xxxxxxxxxxxxxx> wrote: > > 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. > But what do you suggest? I think that create a unique ID for each connected > fd can fix this. Serial code would be responsible to assign the UID. We can play with pipe/splice/tee, but I think that nobody will really gonna need multiple clients per connection. -- Luiz Augusto von Dentz -- 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
