News for hackers. Stuff that matters.
Re:FreeRDP 2.0 – A Remote Desktop Protocol implementation by vel0city on Friday April 10, 2020 @05:41PM (#22837632)
RDP is definitely closer to the framebuffer style rendering than sending explicit draw commands. Newer versions of the RDP protocol have made this very efficient so it only ends up having to transmit compressed data of the changes per frame, but overall its still more of a video-like stream than true local rendering a la X11.
Re:FreeRDP 2.0 – A Remote Desktop Protocol implementation by magicalhippo on Friday April 10, 2020 @06:36PM (#22838046)
> RDP is definitely closer to the framebuffer style rendering than sending explicit draw commands.

RDP has capability[1] to send draw commands directly.

From memory it has had this since the early days. At least I used RDP against NT4 servers over a single ISDN link and it was very smooth. I can't believe it could have done that by streaming bitmaps ala VNC.

[1]: https://docs.microsoft.com/en-us/openspecs/windows_protocols...

Re:FreeRDP 2.0 – A Remote Desktop Protocol implementation by magicalhippo on Friday April 10, 2020 @09:24PM (#22839007)
> From memory it has had this since the early days.

Found an RDesktop implementation from 2001[1] which implements the draw commands. So yeah, old stuff.

[1]: https://soulsphere.org/hacks/rdesktop-sdl/

Re:FreeRDP 2.0 – A Remote Desktop Protocol implementation by moonchild on Friday April 10, 2020 @07:01PM (#22838237)
X network protocol isn't really sending draw commands unless you're using Motif or Xaw or something equally outdated.
Re:FreeRDP 2.0 – A Remote Desktop Protocol implementation by paulirwin on Friday April 10, 2020 @06:03PM (#22837777)
Thanks! I guess I had been misinformed on that. I was also probably thinking of the RemoteFX stuff, like GPU and media redirection: https://en.wikipedia.org/wiki/RemoteFX
Re:FreeRDP 2.0 – A Remote Desktop Protocol implementation by rlkf on Friday April 10, 2020 @07:32PM (#22838454)
No, you are not misinformed. Both RDP and X11 can send both drawing commands and bitmaps. However, as /u/moonchild says, only older programs seems to be sending drawing commands directly. Newer programs want to be fancy and uses toolkits that do their own drawing to have visual effects. (Witness the speed of Emacs vs. editor-du-jour)
Re:FreeRDP 2.0 – A Remote Desktop Protocol implementation by Const-me on Saturday April 11, 2020 @03:28PM (#22843589)
> Newer programs want to be fancy and uses toolkits that do their own drawing to have visual effects

Good toolkits like WPF and UWP implement their own drawing by utilizing Direct3D. These two are using DX 9.0c and D3D 11.0 respectively, and both are supported in RDP protocol.

If you connect to a remote PC and run dxdiag.exe there, you’ll see 3D acceleration is supported, you’ll also see the GPU driver got replaced with completely different one, it’s no longer Intel, Nvidia or AMD, but the one from MS.

This has interesting consequences, e.g. all D3D APIs which move data from system RAM or VRAM or back now become network calls, the system RAM is on the server, VRAM is on the client.

P.S. Modern web browsers use Direct2D and DirectWrite to render stuff on Windows, there’s D3D 11 underneath, i.e. RDP remote rendering is fully supported for browsers and Electron apps.