Hi Johan, On Wed, Dec 12, 2012 at 6:36 AM, Johan Hedberg <johan.hedberg@xxxxxxxxx> wrote: > I agree that Device.Connect should at least work on devices that have > been discovered but on whom we haven't completed service discovery yet. > This would be analogous to the old Adapter.CreateDevice and it'd allow > us to implement proper support for devices not supporting SMP (i.e. > devices you can't call Device.Pair on). What remains to be discussed is > whether Device.Connect is useful for LE devices in some more extended > sense. Maybe it could at least force calling device_set_auto_connect(). On that matter, I would suggest (although I didn't spent much time thinking on the consequences) that Device.Connect should add device to auto connect list, and Device.Disconnect should disconnect current connection and remove device from autoconnect list. For devices which have services implemented inside BlueZ (e.g. HTP), I'm not sure this is a good idea, because these profiles explicitely state on their spec what should happen in case of disconnection, so it is better to have BlueZ handle this for them (IMHO). Regards, -- Anderson Lizardo Instituto Nokia de Tecnologia - INdT Manaus - Brazil -- 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
