> -----Original Message----- > From: Jussi Laako [mailto:jussi.la...@linux.intel.com] > Sent: Tuesday, October 21, 2014 4:15 PM > To: Wang, Quanxian > Cc: ivi@lists.tizen.org > Subject: Re: Simultaneous multi-user multi-seat architecture > > On 21.10.2014 6:02, Wang, Quanxian wrote: > > [Wang, Quanxian] It is very good if you want multiple user to protect > privacy. That is fine. But do you need to bind multiple seat, multiple display > with multiple user. They should not have direct links. I don't think multiple > seat designer like to bind it to multiple users scope. At least for > weston/wayland, they just want to bind it to their own display instead of > multiple-user. > > This is an idea not related with privacy. It is the design idea for your > > multiple > seats, multiple displays. Please don't always bind shared hardware resource > into your multiple user scope. > > One clear example is multiple apps could rendering in one GPU. They don't > need multiple users or single user idea in their rendering process. > > Can you explain how you imagine to handle two keyboards, mice, touch and > displays serving two different users with single GPU? Such way that the two > simultaneous users can only access their own data. At the same time. > [Wang, Quanxian] every user has his display, the display will have its own seat. You bind all assigned devices into the seat which is bound with your display. When you start the apps from your display, its window will be shown on this display and other displays will not show it. You do anything with input devices, others has no any feeling about that(the event is only sent to assigned seat), and will not affect others display(they only receive the assigned seat event).
About your user data, if you be careful, you could use different account to login your facebook. Others could not read your data or don't know what you are doing. If you use website, maybe you have its own cache, it is really a problem. But it is apps problem instead of user problem. Cache sometime is abuse. Always keeping every privacy thing in the cache is not a good custom. So, all the time, multiple customers, one user account, multiple displays, everyone do want you want to do, not conflict with each other. About multiple display process on single GPU, it is up to weston compositor. Weston has the workspace view layer list, you can assign one workspace to assigned display. Every workspace could manage one view list which could be listed on assigned display. When you start the apps, you will make the window be available on the display who start it. In the other display appearance, there is no any change. _______________________________________________ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
