Remote display for Wayland
In order for Wayland to replace X.org it will need to be able to run remote clients like X.org can. The proposed project will pair a proxy compositing server with the client, a psudeo-client with the real compositing server, and enable communication over a network between the psuedo-client and proxy compositor. This will allow normal Wayland clients to be run remotely.
I am not very experienced with the inner workings of X.org or Wayland, so most of my time before May 23 is going to brush up on those, and get the demo clients running.
The wayland protocol specifies a server and a client. The goal is to come up with a proxy client and server that intercept the wayland communication from the client and transmit them over a network to the corresponding server.
More specifically, the software required for this project will be a network proxy compositor and a server on the display host that appears to be a Wayland client from the perspective of the Wayland server and implements a protocol similar to the Remote Framebuffer protocol. The psuedo client on the display host will send the damage events to the proxy compositor, which will feed them to the real Wayland client. The proxy compositor will then receive partial updates from a Wayland client and transmit them to the display host using the RFB-like protocol, which feeds the updates to the framebuffer to the Wayland server.
|File name||Size||Date submitted|