3 ms·
I am just popping up here to say from X10R4 onwards, I have never understood why MIT took a concept we understand around client-server, and completely inverted
by ggm 4y ago
I am just popping up here to say from X10R4 onwards, I have never understood why MIT took a concept we understand around client-server, and completely inverted the meaning for anyone approaching it anew. Here i am connecting to a remote device via a telnet, running an xterm to display "back home". Whats the server? the local thing. Whats the client? the thing I run on the remote host: xterm.
Now step outside X. whats the client? the xterm. Whats the server? the remote host.
Semantic confusion is real folks. "Display server" only partially fixed it because people never remember to vocalise the qualifyer. And then you get Xterminals as physical devices, with "local" clients and now client-server is really really confusing.
- adamius 4y agoThe only way I understand it and stay sane is to say that "the X server serves out access to a display surface which clients like xterm connect to in order to show what they need to show". The X server runs on my machine since that is the display being shared and my programs need a connection to that display. That's the pragmatic explanation I use. Otherwise, and especially if you think servers are somehow always somewhere out there, you'll get a rude counter example. Server just means provider of service and thats about it. You're tripping up on your own assumption. This is why you can telnet/ssh to a server out there, set the display variable to point back to your machine and xterm will try and connect to your machine. Its wanting a connection to your display to show things and to do so it needs a display server, ie yours. That all probably made sense.
- lokedhs 4y agoLet's say you are using a Linux workstation and you fire up ngnix on it to host some web site for testing. You then ssh into a remote server and type "curl https://your-workstation/some-name-here https://your-workstation/some-name-here". In this case, your local machine is the server and curl is the client. This is exactly the same as in the X server case. Your server is running on your machine, and the client is running on the remote machine (which happens to be a server).
- h2odragon 4y agowith X, the resource being served is your eyes. That is not the only instance of "well this was technically correct but confusing and now its Enshrined and May never be Touched all Hail Compatibility" or whatever the impulse for wart retention is. However the whole mess goes to show to me that there is no one true Display System and that there need to be more efforts in this arena, obviously there's still unfilled needs and people feel the compromised currently forced by the available choices are constricting. OpenGL needs yet another networking extension. That'll fix it.