I think what renox was trying to clarify is that the X11 backend in Weston (x11-backend.so) is not XWayland, it's the backend that allows Weston to run inside an X environment. So, if you run Weston inside a running X environment, you get a window that pop up with Weston running inside it. This weston communicates with the running X server and sends its buffer updates to X. This is useful for running Weston when your hardware doesn't support the DRM backend.
Originally Posted by Ericg
XWayland is not a backend per se, ie. you don't run Weston "on" this backend. Instead, as you say, this module listens for applications launched in Weston that try to connect to an X server, and if they do (if it's an old program written specifically for X), then Weston launches an X server, and takes the buffer that the application sends to this spawned X server and displays it as any other application running under Weston.
Looks like this: http://i.imgur.com/lvUbYIb.png
Here you have Google Chrome, gedit, gnome-control-center, gnome-font-viewer, smuxi, synaptic and gnome-terminal running as XWayland clients inside Weston.
Lol okay then
Originally Posted by renox
Has anyone actually managed to connect to wayland/weston via RDP protocol? I've enabled rdp-backend and it seems to be working but when it starts running FreeRDP complains about Address being already in use and it segfaults having negotiated a connection to an external client. Also, when I run weston with rdp-backend enabled then desktop-shell does not seem to be launching at all.
I'm sorry but I am a newbie to wayland/weston devepment and may confuse a few terms.