[Dev] New Tizen Bluetooth Framwork (NTB) wiki page

Xu, Martin martin.xu at intel.com
Mon May 12 13:58:28 GMT 2014


Dominique:
The mulit-user may be the high risk to integrate NTB to Tizen-3.0.
Do you have some wiki or slides for the detail?


From: Le Foll - Intel, Dominique [mailto:dominique.le.foll at intel.com]
Sent: Monday, May 12, 2014 5:43
To: Kis, Zoltan
Cc: Xu, Martin; dev at lists.tizen.org; Liu, Bingwei
Subject: Re: [Dev] New Tizen Bluetooth Framwork (NTB) wiki page

Zoltan,

the issue of using BlueZ directly is linked to the need to enforce the respect of the Application manifest as well as to respect multi user issues.
It can work in a system where application do not have a manifest which tell sin details what they can and cannot do.

 look at https://www.tizen.org/privilege/tizen
 search for bluetoth in the page.

Regards


Dominig ar Foll
(Dominique Le Foll)
Senior Software Architect
Open Source Technology Centre
Intel SSG

2014-05-05 16:55 GMT+02:00 Kis, Zoltan <zoltan.kis at intel.com<mailto:zoltan.kis at intel.com>>:
On Fri, May 2, 2014 at 12:25 AM, Xu, Martin <martin.xu at intel.com<mailto:martin.xu at intel.com>> wrote:
> We have created the wiki page for NTB.
> https://wiki.tizen.org/wiki/NTB_Architecture
>
Hello,

I have some questions for which you likely have answers, but it would
be good to cover them in the document.

1) could you list the more elaborate use cases NTB solves and when NTB
is more useful than direct BlueZ access? If for some use cases one has
to access directly BlueZ anyway, why could not access BlueZ for
everything? That would be more consistent for an app developer, and
wouldn't have to care about possible alignment issues between the
wrapper and BlueZ.

2) for MAP and HFP, can NTB really act as a single proxy agent (single
session) for all apps? to my knowledge, one needs to register the app
for a session, so AFAIK the proxy NTB model would not work. Has this
been reviewed by Comms people (Marcel, Luiz, Johan)?

3) for HFP we prefer handling it not in a bluetooth service daemon,
but in phoned or dialer, since that allows prioritizing the whole call
chain separately and with minimal dependencies.

4.) Other functionality (messaging, contacts etc) may have their own
reasons to use or not to use NTB, and mostly they can already handle
BlueZ directly.
- If you expose the CAPI as a library, what dependencies does it bring?
- If an app does not use NTB, but uses BlueZ directly, what are the
consequences?
- For developers, what makes it worth learning to use a wrapper API,
and having one extra DBUS hop compared to direct access?

Best regards,
Zoltan
_______________________________________________
Dev mailing list
Dev at lists.tizen.org<mailto:Dev at lists.tizen.org>
https://lists.tizen.org/listinfo/dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tizen.org/pipermail/dev/attachments/20140512/d38a9935/attachment.html>


More information about the Dev mailing list