With the 2011 Google Summer of Code, we now know how the Gallium3D OpenCL state tracker
and morphological anti-aliasing
(MLAA) turned out, but how did the remote display capabilities for the Wayland Display Server evolve over the summer? It's something that hasn't yet been reported about on Phoronix.
The aim of the remote display for Wayland GSoC project was to pair a proxy compositing server with the client, a psuedo-client with the real compositing server, and enabling network communication between the pseudo-client and proxy compositor. Under this design, it would then be possible to run Wayland clients remotely in a seamless manner.
Unfortunately, it didn't come too far this summer. There is a remote-wayland repository
on GitHub, but it's currently non-functional. The repository contains the proxy server, proxy client, and remote Wayland client. The student developer behind this code, Jeremy Kemp, wrote a blog post this weekend entitled Turns out it's not as simple as I thought
. This was his first blog post on the subject in more than one month. What's not as simple as he thought is the task of moving data across the network.
His blog post ends, "I've got a (non working) client/server pair that I've posted on github.com/kempj." Hopefully the Texan developer sticks to it and it begins working at some point in the future.