Hi:
> > Because PBAP is not part of the CAPI? See also my email from October
> > 29th that no-one replied to:
> > http://permalink.gmane.org/gmane.comp.handhelds.tizen.devel/4677
>
> Btw, perhaps PBAP does not need to be part of the CAPI if syncevolution API
> provides the same functionality, but I guess that would mean synchronizing
> missed calls, etc, which I guess syncevolution currently ignores. Regarding
> Crosswalk I would have guessed it would make sense to just use D-Bus
> directly so it would work with any platform using BlueZ, if that is not
> possible in Tizen then we have the same problems listed bellow.
Maybe Luiz is right, and CAPI is just used to export the service to upper layer
applications.
I do not think the low level system services must go through Tizen CAPI, like
neard and oFono as the same comms service layer with blueZ can talk with each
other directly.
The good case I think OFono should directly talk with BlueZ to provide the HFP
HF, and so I do not think we need Bluetooth HFP CAPI. And the same thing with
neard. Neard can talk direct with BlueZ to provide OOB feature, and the related
CAPI also do not need. So to PBAP, it maybe another good case. :)
Thanks!
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
