News for hackers. Stuff that matters.
Re:Wayland Architecture by wmf on Friday March 11, 2011 @01:55PM (#2314414)
Wayland can be network-transparent; this is so obvious that the developers didn't bother to explain it (oops). Remote clients will connect to a local proxy server that compresses the window updates (VNC-like) and sends them over the network to a proxy client that decompresses into the appropriate buffers. AFAIK none of this code has been written, but it's not impossible as some people fear.

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.

Re:Wayland Architecture by praptak on Friday March 11, 2011 @02:30PM (#2314539)
Interesting quote by James Gosling (of NeWS fame, among others):

"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."

Re:Wayland Architecture by wmf on Friday March 11, 2011 @02:53PM (#2314636)
Here's the paper that led to Sun Ray:

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."

Re:Wayland Architecture by mansr on Friday March 11, 2011 @02:49PM (#2314620)
This may work fine on a dedicated gigabit network, which is where SunRay lives, but it does not work at all on a slow, possibly high-latency, link. To see for yourself, try running any gtk or qt app over an ADSL link or even a local wireless network, and enjoy the slide-show. Apps using server-side font rendering, on the other hand, work nicely under these circumstances.
Re:Wayland Architecture by lmz on Friday March 11, 2011 @02:56PM (#2314644)
"A pixel copying protocol" would describe VNC and RDP as well, wouldn't it? By running any GTK / Qt app over ADSL you mean running them using the X11 protocol?
Re:Wayland Architecture by sedachv on Friday March 11, 2011 @02:45PM (#2314604)
"Remote clients will connect to a local proxy server that compresses the window updates (VNC-like) and sends them over the network to a proxy client that decompresses into the appropriate buffers."

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.

Re:Wayland Architecture by ezy on Friday March 11, 2011 @02:16PM (#2314489)
See http://en.wikipedia.org/wiki/Xpra as an existence proof. It's an implementation of exactly what you describe using X's existing compositing manager. It has some nice properties over using something like "xmove".