On 17.10.2014 20:00, Jason Ekstrand wrote:
On Thu, Oct 16, 2014 at 9:23 AM, Imran Zaman <imran.za...@gmail.com <mailto:imran.za...@gmail.com>> wrote:This is used for nested compositor architectures. Could you please provide a little more explanation than that. What kind of nesting are you doing?
We have one system compositor using DRM backend and then nested compositors for each user using wayland backend.
This is in order to share single GPU with multiple display outputs among multiple users.
Also, why are you doing this through environment variables and not something explicit? For instance, the compositor can easily grab the socket and chmod it. It has the privileges and knows what socket it is.
This is related to the other patch that allows modifying location of the server/client socket location. I thought that the access control is best being close to the place where socket is created. Otherwise it is hard to follow what is going on if the related code is scattered across modules.
_______________________________________________ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel
