Hi Patrick, >But this doesn't help with the multi-user use cases, does it? It is useful for multi-user PBAP, MAP and so on management.
Not sure it is useful for multi-paired. Best Regards Zheng Wu -----Original Message----- From: Patrick Ohly [mailto:[email protected]] Sent: Tuesday, September 23, 2014 4:05 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 07:32 +0000, Zheng, Wu wrote: > Hi Patrick, > > 1. >Can you describe the entire design, not just what you are changing? I > assume that you will have to add some kind of access control somewhere to > restrict device access. The goal is to explain why these controls cannot be > circumvented. > At current NTB bt daemon use system dbus bus to implement NTB daemon method > call. > > However, if so, NTB daemon only run once. It means that NTB daemon > only run on userA or userB.( system dbus will limit it) > > I will modify the interface method call of NTB daemon to session dbus. > It means that NTB daemon only run on userA and userB. > I don't modify any logic of NTB, just a little modification (modify > system dbus interfaces to session dbus interfaces). But this doesn't help with the multi-user use cases, does it? A device paired by userA will still be available to userB. -- 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
