Le 17/11/2014 20:17, Xu, Martin a écrit :
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
Please note that Tizen 2.x provides CAPI to work on contacts and last
calls. The fact one profile work with PBAP or with an internal modem
should not be visible at the Apps level and so the goal should be to
have one unigied set of APIs..On that point Zoltan is right.
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.
Please note that all profile will not use Sync evolution and so the App
API shall be independent fro the implementation. So direct call to D-Bus
is not the right model.
Getting as close as possible from Tizen 2.x CAPI for message handling is
the right model.
Maybe Luiz is right, and CAPI is just used to export the service to upper layer
applications.
Yes.
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.
Yes system services can do direct call when they are part of the Common
base. Obvioulsy if the are optional component for a profile, then direct
call should be avoided as much as possible.
(e.g. oPhono)
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. :)
HPF should not have it own set of APIs but rather share the Téléphony
API. The only extra step required is the selection of the remote phone
and the swich from hand-free to private mode.
We currently have a dedicated API via Phoned in IVI, but that model will
need to evolve to enable creation of native API which will need to be
aligned between profiles.
Dominig ar Foll
Senior Software Architect
Open Source Technology Centre
Intel SSG
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
