Hi Waldek,
On Fri, Mar 01, 2013, Rymarkiewicz Waldemar wrote:
> >>>>+Blood Pressure Profile hierarchy
> >>>>+================================
> >>>>+
> >>>>+Service org.bluez
> >>>>+Interface org.bluez.BloodPressure1
> >>>>+Object path [variable prefix]/{hci0,hci1,...}/dev_XX_XX_XX_XX_XX_XX
> >>>>+
> >>>>+Properties boolean Intermediate [readonly]
> >>>>+
> >>>>+ True if the device supports intermediate
> >>>>+ measurement notifications.
> >>
> >Couldn't you just return a "NotSupported" error to
> >EnableIntermediateMeasurement?
>
>
> I've just confronted this with the code and this make no sens
> because the watcher passed to EnableIntermediateMeasurement is
> registered on the adapter not for a device. So, it's not possible to
> check if the device supports this feature.
>
> Thus, I will keep Intermediate property for that reason.
Now it makes even less sense. If the EnableIntermediateMeasurement is
per adapter then what use is it to know about whether individual devices
support it or not? The method call will always succeed and the UI will
anyway need to be able to receive intermediate measurements from
arbitrary devices if it has called this method.
So what I'm lacking is a proper explanation of how a UI is supposed to
use this API (in a way that's actually meaningful) as well as why there
is this adapter/device split to begin with (i.e. why the registration
isn't per device or even bluetoothd global).
Johan
--
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
