Originally posted by Remote User
View Post
But by saying that wayland cannot work for you since it removes the network transparent capabilities of X, you are arguing that wayland should be network transparent. And that is not true.
In the modern Linux graphic stack (not limited to wayland), the display server displays (and only read buffers), and the toolkits render, using whatever means and acceleration and API and ABI they like, including through the network if they fancy.
The display server part can do remote displaying like VNC, and I think it has already been demonstrated for Weston with a VNC backend.
Any toolkit can do remote rendering like X11, and it may even have already been done using xlib (server side) and xwayland (client side).
There isn't yet seamless remote rendering in wayland. That's expected because there isn't yet seamless wayland anyway.
But it can be done, and it can be done without wayland having network transparency.
In short, it is not an issue in the design of the modern Linux graphic stack, it is an issue with the fact that this new graphic stack and ecosystem is not feature complete yet (far from it).
Leave a comment: