Hi,
On Tue, Aug 14, 2012, Johan Hedberg wrote:
> Hi,
>
> On Mon, Aug 13, 2012, Rafal Garbat wrote:
> > +Heart Rate Profile hierarchy
> > +============================
> > +
> > +Service org.bluez
> > +Interface org.bluez.HeartRate
> > +Object path [variable prefix]/{hci0,hci1,...}/dev_XX_XX_XX_XX_XX_XX
> > +
> > +Methods dict GetProperties()
> > +
> > + Returns all properties for the interface. See the
> > + Properties section for the available properties.
> > +
> > + RegisterWatcher(object agent)
> > +
> > + Registers a watcher to monitor heart rate measurements.
> > +
> > + Possible Errors: org.bluez.Error.InvalidArguments
>
> I'm wondering if it wouldn't make more sense to have these
> RegisterWatcher APIs (thermometer, heart rate, others?) per-adapter
> instead of per-device. That would be much friendlier to applications in
> that they wouldn't need to separately search for paired/configured
> devices supporting a specific service. Moving this to be per-adapter
> would also mean that the first parameter of the Watcher methods would be
> the object path of which device is in question.
So any comments on this? I'd like to get this moving forward and finally
merged upstream.
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
