Re: Health Thermomether Profile

Hello Elvis,

2011/6/9 Elvis Pfutzenreuter [off-list ref]:

On Jun 9, 2011, at 11:09 AM, Santiago Carot wrote:

Hello,

I was thinking in to get my hands on this stuff. First of all, I would
like to know if there are people working in this profile to join and
callaborate with them in the development tasks (if it would be
possible), if not, I would like to start with the development of this
profile as soon as we agree a proper desgin, API and so with all of
you.

Count me in.

Cool,

I have worked on a server implementation:
https://gitorious.org/bluez-epx/bluez-epx/commits/thermometer

Next I'm going to explain some light ideas that round my head:

At first I was thinking to attack the attribute D-Bus API due that
health thermomether profile is placed over GATT, but I don't see how
it fits into BlueZ architecture because it will force us to use the
attribute D-Bus API to provide another Thermomether API through D-Bus.
It seems me quite ugly.

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.

There is another possibility: transcoding. The whitepaper has been
published. In theory this gives the possibility of giving access to
LE health devices via HDP API.
I feel that two approaches (profile specific API and transcoding support)
are not mutually exclusive, both could be pursued, and doing transcoding
implies having colletor-side profile support in place.

I'm not familiarized with transcoding, I'm going to get into that
white paper right away. Thanks for the pointer.

These are only rough ideas so I really appreciate comments and
suggestion from your side before starting.

Regards.
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth"
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html