RDP Back-End Merged For Wayland's Weston
One month ago a FreeRDP-based remote compositor for Wayland's Weston was proposed. Now having undergone six code revisions, the Weston Remote Desktop Protocol back-end has been merged.
This RDP back-end to Weston waits for RDP clients to connect and then sends frame-updates to these clients. Each RDP client has its own seat -- thereby being multi-seat friendly in Weston -- and frame updates can be done with surfaces or the RemoteFX codec. FreeRDP is in compliant with most of Microsoft's RDP 7.1 protocol.
This early remote display back-end for Weston now lives along with the DRM, Wayland, Headless, and FBDEV frame-buffer back-ends in mainline Weston.
The RDP compositor code adds just over 1,000 lines of code and was merged with this commit. Enabling the Remote Desktop Protocol support requires the --enable-rdp-compositor switch at compile-time.
This RDP back-end to Weston waits for RDP clients to connect and then sends frame-updates to these clients. Each RDP client has its own seat -- thereby being multi-seat friendly in Weston -- and frame updates can be done with surfaces or the RemoteFX codec. FreeRDP is in compliant with most of Microsoft's RDP 7.1 protocol.
This early remote display back-end for Weston now lives along with the DRM, Wayland, Headless, and FBDEV frame-buffer back-ends in mainline Weston.
The RDP compositor code adds just over 1,000 lines of code and was merged with this commit. Enabling the Remote Desktop Protocol support requires the --enable-rdp-compositor switch at compile-time.
5 Comments