Hi Johan,
> > +Service org.bluez
> > +Interface org.bluez.OOB
> > +Object path /org/bluez
>
> I think this should use the same path as the Manager API, which at the
> moment is /
I was following HealthManager way, but I'm fine if you prefer / path.
> > + array{byte} hash, array{byte} randomizer
> > + ReadLocalOobData(object adapter)
>
> Having to pass an adapter path as a parameter seems weird. Wouldn't it
> make more sense to have this method in the Adapter path/interface
> instead? Also, we could toy around with the thought of putting the two
> other methods into the current Manager interface.
It is OK to me to move ReadLocalOobData to adapter path as this is an adapter
related data.
My initial idea was to keep all oob related methods in org.bluez.OOB interface
but I'm not going to insist on it.
--
Szymon Janc
on behalf of ST-Ericsson
--
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
