Comment by miki123211
2 years ago
You still had to do a roundtrip for every single click though, right? I don't think X Windows has any kind of client side scripting system.
That's better than SSH for sure, but still not as good as the web model.
2 years ago
You still had to do a roundtrip for every single click though, right? I don't think X Windows has any kind of client side scripting system.
That's better than SSH for sure, but still not as good as the web model.
X Windows server runs on the client machine.
The client is the server application.
The point still stands, though. You need a roundtrip, even if it starts from the X server rather than the X client.
You always need some level of round trip between keyboard and UNIX procecess.
The server application isn't guessing keys, regardless of the connection format.
What matters is how the communication is being compressed and local optimizations.
12 replies →
I'm sorry to say I'm as confused as I was before I read these sentences.
Let me try to rephrase: with X Windows, the UI server runs on your local machine, while the UI client runs on the remote machine (e.g. your application's server). Is that correct?
No, the whole UI runs on the client machine, which in X Windows nomenclature is the server.
The client application (on X Windows nomenclature), runs on the remote server and is headless.
Instead of sending streams of bytes to render text, it sends streams of encoded X Windows commands to draw the UI.
Everything else regarding compilers, subprocesses and what have you keeps running on the server, regardless how the connection is made.
Think big X Windows terminals or green/ambar phosphor terminals accessing the single UNIX server, used by the complete university department.
3 replies →