3 ms·
"High latency nature of the protocol" is a bit misleading. X is distinctly asynchronous. You don't send the server a command and then wait till it ack's that b
by PaulDavisThe1st 4y ago
"High latency nature of the protocol" is a bit misleading.
X is distinctly asynchronous. You don't send the server a command and then wait till it ack's that before doing something else. The actual delay between the client sending the command and the result appearing on the server's display can be extremely fast (dependent mostly on network performance), and by most definitions that is a "low latency" system. However, if the app on the client needs more synchronous behavior from the server, that's when you start to see things slow down and demonstrate "high latency"
- hedora 4y agoI believe it is impossible for an RDP app to rely on "more synchronous behavior" as you put it. Remote X11 worked well in the past. It's possible to latency-optimize software for it, but it's not common anymore.
- mekster 4y agoI wonder why cloud vendors, even AWS, wouldn't invent a modern remote desktop protocol that works cross platform in easy way such as through ssh protocol that may perform at near native performance and they may just have a wider use case for cloud servers to increase their revenue. Of course it helps other vendors too but no one loses including the users.
- yjftsjthsd-h 4y agoAWS apparently has implemented something that works decently and cross platform, but AFAICT they're not sharing. The best docs I can find in a hurry are https://aws.amazon.com/workspaces/faqs/?nc=sn&loc=4 https://aws.amazon.com/workspaces/faqs/?nc=sn&loc=4 which talks about it not being RDP and only supporting connecting via their custom client.