5 ms·

I also wished that was true while working on a fast web-based remote desktop client. Imagine if instead of a video stream via VNC, the UI was HTML or SVG diffs.

• crazygringo 4y ago
  Yes! IIRC, RDP was originally based on simply sending over the GDI calls -- the Windows draw instructions -- directly. I've been told it moved away from that as networks got faster, interfaces became more GPU-accelerated, and video encoding became hardware-accelerated, so that now it's not much different from VNC. But I don't know when or to what extent, or if RDP still uses any draw instructions at all.
  • mmastrac 4y ago
    RDP most likely uses privileged instrumentation to detect screen damage, rather than having to do a full framebuffer scan (or getting framebuffer damage bounds) to identify diffs.
  • digitallyfree 4y ago
    Modern RDP can use hardware h.264 encoding if your GPU supports it, and grabs the output from the framebuffer and streams it like a game streaming app does. I think the default RDP mode still sends the draw commands the old-fashioned way though.
• joshspankit 4y ago
  There was a tool called radmin back in the [days before it was heavily commercialized then ruined] that still to this day is the absolute fastest remote desktop setup I’ve ever used. I’d be surprised if it was more than 20ms + network latency. I suspect that it transferred OS calls. But even then, that would pale in comparison to SVG diffs from an SVG-native OS.