Hello;

in order toe help people who do not have the time to deep in the code, Corentin has done a detailed analysis of mapping the App manifest against the CAPI for Bluetooth.

Bluetooth is interesting because the creation of a demon service was required to add sharing persistance between Apps and multiuser support what is not simple to do directly from the BlueZ API (not to say not really possible). Without a Demon sharing a device by multiple users, using a device already paired by an App with an other App or enabling automatic reconnection (IVI requirement) is far from simple.

You will notice that beside of the "getKnownDevice" method all the App manifest features fit well to the existing CAPI

Enjoy the reading.

https://docs.google.com/a/fridu.net/spreadsheets/d/1c6fy3ZUIeAai3wxwITahP14R1W4DEpfEqHNcESX-h-Q/edit#gid=0

--
Dominig ar Foll
Senior Software Architect
Open Source Technology Centre
Intel SSG

_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev

Reply via email to