Not logged in
Log in now
Create an account
Subscribe to LWN
LWN.net Weekly Edition for December 5, 2013
Deadline scheduling: coming soon?
LWN.net Weekly Edition for November 27, 2013
ACPI for ARM?
LWN.net Weekly Edition for November 21, 2013
For a real example, Windows RDP supports single app remoteing...and they sure don't use X11. It works damn well -- better than X11 forwarding.
The way to Wayland: Preparing for life After X
Posted Nov 18, 2010 16:38 UTC (Thu) by rwmj (subscriber, #5474)
Pixels are not the same shape on every display. Colours aren't balanced the same way.
The application really needs to talk to the display to find out these things, which is exactly how X works, and how the other technologies you mentioned do not. (I should also mention that actual rootless VNC/whatever that *I can use today* does not exist).
Posted Nov 18, 2010 17:42 UTC (Thu) by foom (subscriber, #14868)
But RDP gets a lot of other things right, which Unix/X11 forwarding doesn't: sound devices, filesystem, and printers are all shared from the desktop client to the server.
Yes, sure, those are all "simple" additions on top of X11 (or perhaps beside it). Just like color calibration and pixel shape are to RDP.
Posted Nov 18, 2010 23:52 UTC (Thu) by intgr (subscriber, #39733)
You forgot performance. I've tried using X11 forwarding over SSH on a 100Mbit LAN. Maybe I'm doing somethng wrong, but I always found the performance to be abysmal. They say it's GTK's fault, but what's the point of a feature if major toolkits can't find developers to work on properly supporting it? As it stands, I couldn't care less about X11's network transparency.
RDP, on the other hand, flies even over a regular DSL connection. That's more important than getting color profiles right.
Posted Nov 21, 2010 17:36 UTC (Sun) by nix (subscriber, #2304)
X is really rather good over LANs. It's latency that kills it.
Posted Nov 19, 2010 2:21 UTC (Fri) by dlang (✭ supporter ✭, #313)
sound is an issue in some cases.
Posted Nov 23, 2010 5:06 UTC (Tue) by foom (subscriber, #14868)
Filesystems (and printers) aren't otherwise *easily* shared from client to server, in a way such that the app running on the central server can access your client's filesystems and printers.
Of course you can turn on NFS on your client, set things up so that it's securely and encrypted, become root on the server, mount your client's file share...then undo all that again when you stop using the remote app. But that's anything but easy. MS Remote Desktop makes it *easy*. (I suspect that functionality is not actually part of the display protocol, but rather just using a tunnel through the same encrypted connection, but still it's very nice for the client to handle all of that)
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds