Hello all, I permit to add some details about this notes: *But that remains to the decision of the platform creator who may decide to use or not to use a guest pre-login user model.*
We can't use application framework if you are not identified. In case where the platform creator doesn't choose the guest prel-login user model, this means that as long as the user is not identified or identified as guest, the user *can't use* application framework. Thanks to take it in account. BR Baptiste 2014-07-09 12:50 GMT+02:00 Dominig Ar Foll <[email protected]>: > > > > 2014-07-09 10:15 GMT+02:00 김태수 <[email protected]>: > > 1. Multi-guest case >> >> I can see only one guest whose ID is "guest" on NUC kit. (Tizen 3.0 >> Common binary) If several guests connect to the system, I think ID of each >> guest should be like "guest1", "guest2"... >> >> Is it right? >> >> And if right, is it planned to implement this? >> > To be honest you create as many user as you want with the name that you > want. As you will see on the Wiki, there is no pre definition of user name > but you can declare applications to be visible by : > - all user (including guest(s) > - all logged users > - only one user > >> >> >> 2. Default log-in user >> >> According to the document, guest user will be connected before login. >> >> Can you tell me any scenario for this?? >> >> IMHO, to turn on the IVI system, driver(main user) should start car with >> key first. >> >> That means the main user authentication is already done, so main user >> should be default log-in user. >> > Tizen is targeting multiple platforms and does not assume any type of > special login mode but in general very availability of some base > application is expected eg: > - live TV playing last channel for TV > - showing the time for a watch > - playing the last tune in radio and rear view camera for a car. > > Having a guest user allows to start these applications in advance of the > burden induced by the login in a named user account which will likely drag > many configuration options and new applications can be very nice. > > But that remains to the decision of the platform creator who may decide to > use or not to use a guest pre-login user model. > > My expectation is that keys are often shared in a car and so not great for > a full login that could include access to private data (do you want the > next person hiring a car to see your previous last phone calls or > destination and route details?). It's OK for seat, mirrors and radio > adjustments but more will likely not be acceptable for private data access. > > NFC with on the user phone may be an option, but will require the user to > place the phone in a specific position, facial camera detection or finger > print could also be OK. At the end, our issue in Tizen is not to decide how > to do it , but to enable it to be done as platform maker will want it done > :-) > > -- > Dominig ar Foll > Senior Software Architect > Intel Open Source Technology Centre > > _______________________________________________ > Dev mailing list > [email protected] > https://lists.tizen.org/listinfo/dev > > -- Baptiste DURAND Eurogiciel Vannes/FR
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
