Comment Re:time to die... (Score 2) 204
Worse yet, all of those round trips are done synchronously. If the goal is network transparency, X is awful no matter how you slice it.
It is desirable to minimize the display to input path for interactive applications, and I'd love for the ability to use tablets as a custom interactive input panel for desktop applications. There will always be a delay in the event processing loop of an application, but I believe that this is the one which should be minimized, allowing truly interactive multitouch or pen based controls to be created. Then, for remote applications, one can move the control surfaces to the local display.
It isn't clear that this needs to be baked into the protocol, and may work fine as an API on top of a minimal system like wayland. Putting this logic into the display server may not be flexible enough, as one could imagine a whole spectrum of uses. At one extreme, the whole application could be running local (on your remote display). Then, perhaps only the filesystem, network, or other OS services could be proxied, and so forth. Creating a truly universal protocol is a daunting if not impossible task.