On 22.10.2014 11:29, Lukasz Pawelczyk wrote:
So why are you so against preserving them?
Preserving WHAT!?
This discussion went sideways at least 10 emails ago. All that was said
was not to merge multi-seat/multi-display with multi-user on the
implementation (weston/wayland) side.
We have requirement for multi-user multi-seat IVI, so what are you
suggesting to do?
How do you suggest multi-user and their data privacy to work and
associate this with multi-seat setup?
Please write a wiki page and explain (also with pictures) how it will
work while fulfilling the IVI multi-user requirements in JIRA.
All the rest is one big misunderstanding because people understood that
mr. Wang wanted multi-seat/multi-display without multi-user in the end
product.
So what does following mean then?
--- begin quote ---
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.
--- end quote ---
Each active user MUST have their own UID and their processes run under
their own UID. Data stored by the application running under user's UID
goes to this UID's home directory. Standard multi-user Linux stuff. I
personally don't want to see any other way of implementing multi-user
because it will break security of pretty much all existing open source code.
Each simultaneous guest (anonymous) user have their own UID and home
directory that is cleaned up when the session is terminated. This is
also in requirements.
_______________________________________________
IVI mailing list
[email protected]
https://lists.tizen.org/listinfo/ivi
