[Dev] NTB multi-user compliancy
wu.zheng at intel.com
Tue Sep 2 09:44:08 GMT 2014
> The current design is an 'app' single user design. It needs to be adapted to allow multi-user feature.
I mean that the current design is that bluetooth-frwk doesn't run on root user.
However, It can run on the each user (such as user1, user2, tizen, app and so on).
The reason is that obexd features is included in bluetooth-frwk and obexd only run on each user not root user.
Therefore, I don't make sure that multi-user feature should be added to bluetooth-frwk.
The reason is that Bluetooth-frwk only run on each user not root user.
From: Corentin Lecouvey [mailto:corentin.lecouvey at open.eurogiciel.org]
Sent: Tuesday, September 2, 2014 5:25 PM
To: Zheng, Wu
Cc: dev at lists.tizen.org
Subject: NTB multi-user compliancy
Hi Zheng Wu,
>> Is there a reason to run it as app user ?
>> It should be run on root mode.
> Obex related features are necessary on app mode.
> Therefore, Our Bluetooht-Frwk need to run on app mode.
> Or Our Bluetooht-Frwk will miss the obex related features.
> The current design is that Bluetooht-Frwk run on app mode.
The current design is an 'app' single user design. It needs to be adapted to allow multi-user feature.
Obex related features would be adapted to not depend on only 'app' user.
obexd is a user daemon so it should be able to run for each user.
More information about the Dev