3 ms·
As you say, anything networked X can do, VNC can do better. I can't help but think, though, that the arrangement we have now—where VNC servers on ⋆nix are imple
by derefr 10y ago
As you say, anything networked X can do, VNC can do better. I can't help but think, though, that the arrangement we have now—where VNC servers on ⋆nix are implemented in terms of being a sort of pixbuf caching proxy for the local X server—is actually a nice, optimal arrangement that allows for a good separation of concerns.
It's a bit like Mapbox: you've got a database full of semantic geometry state that applications can poke (the X server), and then you've got a fronting daemon that renders, serves, and caches graphical "tiles" created by querying that geometry (the VNC server), along with exposing a protocol through which clients can easily poke at the database by referring to it in terms of the tile-server's screen coordinates.
Also, other people might say it's clumsy, but personally I really enjoy the architecture of containerized GUI apps: you've got xvfb running in the container as an X server, and then x11vnc or the like also running in there, talking to xvfb, serving VNC "tiles" and receiving key and pointer inputs over a socket. It's like the OSI network layers: X11 is the application layer, VNC is the presentation layer.
- bandrami 10y agoanything networked X can do, VNC can do better VNC does single window clients which interact with the primary and secondary selections on the display server now?