Hi Patrick, >Why would NTB need to be changed? My understanding at the moment is that NTB >runs as normal user, and thus inherits this behavior from the kernel >automatically. Yes. NTB will be implemented as that NTB runs as normal user, and thus inherits this behavior from the kernel automatically.
>Better: a device can be paired for one user and only used by that user; other >devices get paired for use by all users (keyboards, for example). I can understand a device can be paired for one user and only used by that user; >other devices get paired for use by all users UserA has paired with DeviceL and UserA can use the related service of DeviceL. If UserB want to use the related service of DeviceL, how can UserB do? (UserA and UserB is in the same DeviceA). Best Regards Zheng Wu -----Original Message----- From: Patrick Ohly [mailto:[email protected]] Sent: Tuesday, September 23, 2014 2:25 PM To: Zheng, Wu Cc: [email protected]; Le Foll, Dominique; [email protected] Subject: Re: [Dev] FW: Tizen 3 services: use case for multi user On Tue, 2014-09-23 at 05:19 +0000, Zheng, Wu wrote: > Hi Corentin and Patrick, > > I just want to double check the multi-pairing use case. > > >> BlueZ 5 persistently pairs remote devices, which brings up a use > >> case for multi-pairing : > >> UserA is paired and connected to deviceR. When userA is > >> disconnected from deviceR, userA stays paired. > >> In such case, a new user (userB) logins to the system and he is > >> automaticaly paired to deviceR without any authentication. > >> As userB is already paired with the remote deviceR, he can just > >> connect to PBAP service from deviceR to retrieve the phonebook for example. > > 1. Is it a first acceptable phase for multi-pairing? This is the current status. It's considered undesirable. I don't know whether improving on that is considered essential for NTB to be accepted. > If so, NTB will try to implement and match it, so that NTB can be > integrated to Tizen.org. Why would NTB need to be changed? My understanding at the moment is that NTB runs as normal user, and thus inherits this behavior from the kernel automatically. > If yes, it is good that you can add the related requirement in > https://wiki.tizen.org/wiki/Multi-user_Bluetooth? As I said to Corentin, this is not a requirement. The request was to *avoid* this scenario. > 2. If not, which scenario is the weaker requirement of multi-pairing? > So that we can check the current NTB status. Weakest (too weak?): any paired device can be used by any user. Better: a device can be paired for one user and only used by that user; other devices get paired for use by all users (keyboards, for example). Best: a device can be paired for an arbitrary set of users. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
