Hi, Apparently you guys are not synchronizing with Bluetooth, anyway this looks better but if you are doing a blocking call to GetConnectionUnixUser perhaps it is better to use dbus_bus_get_unix_user since it is probably doing the same thing anyway.
On Fri, Oct 17, 2014 at 9:22 AM, Zhang, Zhengguang <zhengguang.zh...@intel.com> wrote: > Hi, Dominique > > We have finished the phrase 1 source code in ConnMan to meet WiNet > multi-user requirements, and submitted them to gerrit: > > https://review.tizen.org/gerrit/#/c/28918/ > > https://review.tizen.org/gerrit/#/c/28921/ > > https://review.tizen.org/gerrit/#/c/28922/ > > https://review.tizen.org/gerrit/#/c/28923/ > > https://review.tizen.org/gerrit/#/c/28924/ > > > > I have verified the solution and found it can meet the requirements, please > help to review the patches and any suggestions, feel free to let me know, > thanks in advance! > > > > > > Regards, > > Zhang Zhengguang > > > > From: Dev [mailto:dev-boun...@lists.tizen.org] On Behalf Of Dominig ar Foll > (Intel OTC) > Sent: Wednesday, October 8, 2014 4:30 PM > Cc: dev@lists.tizen.org > Subject: Re: [Dev] winet multi-user feature > > > > Zhang, > > happy to see that you have plan to deliver the required feature. > When will we see the code ? > > "Nicolas Guyomard" <nicolas.guyom...@open.eurogiciel.org> will be the > engineer in charge of the integration in Common once your code is ready. > He is present on this list. > > Regards > > Dominig ar Foll > > Senior Software Architect > > Open Source Technology Centre > > Intel SSG > > Le 08/10/2014 10:03, Zhang, Zhengguang a écrit : > > Hi, Dominique > > After our investigation about how to implement WiNet multi-user > requirements, we found that it’s the right way to implement it in ConnMan, > the reason is described below: > > 1. ConnMan is the real connection manager daemon, and it should handle > multi-user related stuff logically. WiNet service daemon is only a slim > daemon which is designed to make some background operations, such as trigger > periodically scan, tethering data statistics and son on. > > > > 2. ConnMan has already supported a feature “Session” which can be used > to implement multi-user, but we found that it’s not mature enough and a > little too complicated, after a balance about the schedule and the solution, > our proposal solution is: > > 1). At the first phrase, add ConnMan patches ourselves to implement > multi-user and maintain them in Tizen ConnMan, by our investigation, we only > need less than 5 patches to implement the requirement. It’s not a problem to > maintain the related patches in Tizen and not submit them to upstream, > actually, we have already maintained more than 20 patches in Tizen ConnMan > to meet Samsung specific requirements, which can’t be merged into ConnMan > upstream. So Tizen ConnMan is a little different with upstream Connman: > upstream ConnMan is common to every platform, but Tizen ConnMan is specific > for Tizen platform. > > 2). At the second phrase, when multi-user requirements is nailed down > completely and ConnMan session is mature, we will continue to investigate it > and try to switch the solution to ConnMan session. > > > > Currently at the first stage, we will submit the related patches to gerrit, > we will add you guys as the reviewers, any suggestions about it, feel free > to let me know, thanks! > > > > > > Regards, > > Zhang Zhengguang > > > > > > > _______________________________________________ > Dev mailing list > Dev@lists.tizen.org > https://lists.tizen.org/listinfo/dev > _______________________________________________ Dev mailing list Dev@lists.tizen.org https://lists.tizen.org/listinfo/dev
