Ok, lemme get this right...

Quote Originally Posted by Nobu
In other words, you could launch [RDP_Compositor] and have your desktop compositor run underneath it, and/or run your desktop compositor and have [RDP_Compositor] run under it. Or, your desktop compositor could be [RDP_Compositor].
So, comparing this to vnc. First variant would be starting Xvnc being rendered locally yet viewed over the RFB protocol (which is optionally locally possible). This is comparable to a server with thin clients (right?). And the second variant would be running X locally, and have x11vnc polling for changes and making those available as an RFB stream (like me assisting my parents).

But this time, it's integrated into the compositor in the new Wayland 'model'.

Quote Originally Posted by renox
1) Yes until we get a library that can just supply all possible backends (probably a good idea for someone to write) to any wayland compositor that wants it... until then, every compositor has to implement this on their own.
So, something like: a compositor (e.g. Weston) depending on a library (e.g. librender). This librender depends on libfreerdp, libvnc, libnx or whatever. So whatever compositor links against librender get's the rest for free. Would be nice.

Quote Originally Posted by EricG
The answer to this is: it depends, if the other compositor is able to use Wayland as its back-end (Weston can do this) then you can nest/stack them..
So, instead of what renox said: You write a compositor purely for RDP and another compositor purely for VNC and stack that on a compositor currently rendering on a local backend (like DRM or FB).

Quote Originally Posted by elanthis
Since you can nest Wayland compositors... anRDP "client" can be started and run I ER any other compositor. Similar-ish to how you can use any text shell, since sshd handles the networking, not the shell itself.
But for that to work, you need screen to manage this shell in order for this terminal to be available both locally and remotely. I guess Wayland is analogue to screen in this case?

Quote Originally Posted by giselher
Weston is able to run as x11 client with the x11_backend (like XNest or Xephyr) and it is also able to run on a tty with the drm or fbdev backend. The headless backend is just for testing and debugging the wayland code independent of the backend (the functions are just stubs). They wayland backend lets you run a wayland compositor as wayland client/window (also like XNest).
But you still need Wayland for every backend, right? E.g. gtk is ported to Wayland. So you should get GTK+ -> Wayland -> Weston -> FBDev. And not GTK+ -> Weston -> FBDev. And the final step depends on Weston supporting whatever back-end you want it to.



This is getting 'interesting'. X was split into Wayland and Weston. Okay, so one could say that Wayland is purely a middelman that connects toolkits to your screen. But to manage your screen you use a compositor that responds on user input. I follow on that. Now, this compositor get's all sorts of plugins. BUT, the functionality those plugins provide could also be used by (supposedly) other (stacked of course) compositors. So you have 2 ways of implementing the same functionality. Just one is compositor specific and the other one is not. However, the compositor specific method could be build into a library so that all the compositors that link to it recieve that same functionality.

Please understand that I don't quite follow the general idea anymore...