"I think that a more viable solution in the long run would be to replace the X protocol with a very simple pixel copying protocol that uses the user-level rendering libraries in the application to render to a local image buffer, then copies the pixels over the net in something that looks vaguely like a video stream.
There are a variety of compression hacks that make this surprisingly efficient – this is essentially what the SunRay product does. Some analysis has been done that shows that this uses essentially the same bandwidth as the X protocol, if done well."
From "Window System Design: If I had it to do over again in 2002."
http://labs.oracle.com/features/tenyears/volcd/papers/nrthcu...
http://labs.oracle.com/features/tenyears/volcd/papers/Nrthcu...
Their argument is "A simple pixel encoding protocol requires only modest network resources (as little as a 1Mbps home connection) and is quite competitive with the X protocol."
By that definition everything is network-transparent. Can this do caching of glyphs? Images? All the lessons learned from X and incorporated into NX are ignored. NX is actually usable across high-latency, low-bandwidth links. Streaming bitmaps aren't.
Now it may happen that no one cares enough about network transparency to bother to write the code, but I don't see that as Wayland's problem.