seprate window management component

[cat]

well if clients are allowed to decide how their own windows stack, the
window management proxy would be in control.

the idea I have is that there isn't any special protocol changes
(though that might be bad for this system), but because of the proxy,
a call to or a response from (or lack of one) a client could be
corrected, and nether the final display server nor the client know
that such a correction took place.

to better enforce the use of such a proxy, a display server could only
accept a connection from one client

On Wed, Sep 14, 2011 at 10:19 AM, Michal Suchanek <hramrach at centrum.cz> wrote:
> Hello,
>
> On 14 September 2011 16:55, cat <zixon65 at gmail.com> wrote:
>> would it be to much trouble to make window management a proxy program?
>
> The wayland server has to know how the windows stack but the clients
> are not trusted to tell it how the windows should stack so either the
> server has to figure that out by itself or a separate privileged
> component (eg. a proxy or a plugin or attached process of some sort)
> would need to decide that.
>
> I thought that it would make sense to determine what policy needs to
> be decided by this manager and add protocol for it in Wayland even if
> the default implementation will just grant every request an
> application ever makes.
>
> When I asked about that it was not outright rejected but there was
> nobody else who though putting some structure into Wayland would be of
> any use.
>
> I guess this will be considered only after Wayland evolves so many
> warts as X has and putting some sanity in the protocol will be
> impossible at that point for reasons of backward compatibility and
> whatnot.
>
> Thanks
>
> Michal
>