The irony

Posted Nov 5, 2010 4:17 UTC (Fri) by dlang (guest, #313)
In reply to: The irony by davide.del.vento
Parent article: Shuttleworth: Unity on Wayland

the time it takes to make the network hop to the server over a local gig-E network is so small that it just doesn't matter. The message will travel faster than your system will time-slice with a jiffies setting ao 100Hz

over high-latency links X performs poorly because it serializes everything and so you have a huge number of round trips, but since these are very standard messages that have the same answer for all applications, most of this data can be cached and replied to locally, eliminating the network latency. there's still the message passing and parsing latency, and most of these messages could be combined to save that, but still keep the network transparency in place.

The irony

Posted Nov 5, 2010 13:30 UTC (Fri) by rgoates (guest, #3280) [Link] (1 responses)

The last time I checked (which has been several years), an interactive X session sends a network packet for each and every keystroke. A horrible waste of bandwidth, but I'm not sure how you can improve that without affecting interactivity (or significantly changing the client-server model X is built around).

The irony

Posted Nov 6, 2010 3:42 UTC (Sat) by mfedyk (guest, #55303) [Link]

just like..... ssh.

please explain why nx hasn't become the wire protocol for x...