On 22.10.2014 8:07, Wang, Quanxian wrote:
[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).
Yes, we have this functional already.
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.
Each user now runs under their own UID and home directory and thus cannot get their data mixed by malicious on misbehaving applications.
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.
This is possible to do already, but this is not what multi-user Tizen does by default. And shouldn't be used as it is very vulnerable.
There would be nothing preventing malicious user or applications from accessing other user's data.
_______________________________________________ IVI mailing list [email protected] https://lists.tizen.org/listinfo/ivi
