On Thu, Jun 9, 2011 at 10:09 AM, Santiago Carot <sancane@xxxxxxxxx> wrote: > On the other hand, lastest Anderson's e-mails about GATT make me think > other designs avoiding attribute D-Bus API by using GATT direclty to > implement the Thermomether client profile. In this way we can make a > bluetooth plugin wich exposes the client part through D-Bus API to > manage Thermomether devices by hiding GATT profile to applications > that only want to operate over this kind of devices. I think that it's > a pretty design wich fits better in BlueZ. Actually this is exactly what we have been doing for profiles not yet adopted. It seems to fit better next to other non-GATT profiles, each having it's own D-Bus interface documented in doc/*-api.txt files. Feel free to suggest a draft API (in the format of doc/*-api.txt files), it is much easier/cheap than attempting to implement code so to have to rewrite it later (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
