Are “sockets” addressing a display of a X server and connected to or created by X client the same...












-1
















  • A X server is said to be started in a display. The address of a display is specified as a socket by $DISPLAY. For example if $DISPLAY is :40, it corresponds to a port 6040 or a unix domain socket named after 40.


  • A X client and a X server communicate by sockets.



What does the socket specified by $DISPLAY in the first sentence mean?



Are "socket" addressing a display of a X server (in the first sentence) and "socket" created by a X server and connected to a X client (in the second sentence) the same "socket"?



But I don't think they are the same socket, because I think



X client <->  X server <-> display


so a X client and a display are not connected directly but indirectly via a X server. So a X client can't communicate directly with the display addressed by $DISPLAY?



Thanks.










share|improve this question

























  • unix.stackexchange.com/questions/503870/… So most phrases used in your question is meaningless. An X server is a display. Use the right syntax :40 or HOSTNAME:40, not 40. X client and X server communicates with X11 protocol(over TCP or UDS), not nessacarily sockets because some platform doesn't have it. For linux, sockets or any file can't be owned by a process, linux doesn't have this concept.

    – 炸鱼薯条德里克
    27 mins ago
















-1
















  • A X server is said to be started in a display. The address of a display is specified as a socket by $DISPLAY. For example if $DISPLAY is :40, it corresponds to a port 6040 or a unix domain socket named after 40.


  • A X client and a X server communicate by sockets.



What does the socket specified by $DISPLAY in the first sentence mean?



Are "socket" addressing a display of a X server (in the first sentence) and "socket" created by a X server and connected to a X client (in the second sentence) the same "socket"?



But I don't think they are the same socket, because I think



X client <->  X server <-> display


so a X client and a display are not connected directly but indirectly via a X server. So a X client can't communicate directly with the display addressed by $DISPLAY?



Thanks.










share|improve this question

























  • unix.stackexchange.com/questions/503870/… So most phrases used in your question is meaningless. An X server is a display. Use the right syntax :40 or HOSTNAME:40, not 40. X client and X server communicates with X11 protocol(over TCP or UDS), not nessacarily sockets because some platform doesn't have it. For linux, sockets or any file can't be owned by a process, linux doesn't have this concept.

    – 炸鱼薯条德里克
    27 mins ago














-1












-1








-1









  • A X server is said to be started in a display. The address of a display is specified as a socket by $DISPLAY. For example if $DISPLAY is :40, it corresponds to a port 6040 or a unix domain socket named after 40.


  • A X client and a X server communicate by sockets.



What does the socket specified by $DISPLAY in the first sentence mean?



Are "socket" addressing a display of a X server (in the first sentence) and "socket" created by a X server and connected to a X client (in the second sentence) the same "socket"?



But I don't think they are the same socket, because I think



X client <->  X server <-> display


so a X client and a display are not connected directly but indirectly via a X server. So a X client can't communicate directly with the display addressed by $DISPLAY?



Thanks.










share|improve this question

















  • A X server is said to be started in a display. The address of a display is specified as a socket by $DISPLAY. For example if $DISPLAY is :40, it corresponds to a port 6040 or a unix domain socket named after 40.


  • A X client and a X server communicate by sockets.



What does the socket specified by $DISPLAY in the first sentence mean?



Are "socket" addressing a display of a X server (in the first sentence) and "socket" created by a X server and connected to a X client (in the second sentence) the same "socket"?



But I don't think they are the same socket, because I think



X client <->  X server <-> display


so a X client and a display are not connected directly but indirectly via a X server. So a X client can't communicate directly with the display addressed by $DISPLAY?



Thanks.







display x-server






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 23 mins ago







Tim

















asked 42 mins ago









TimTim

27.7k78264483




27.7k78264483













  • unix.stackexchange.com/questions/503870/… So most phrases used in your question is meaningless. An X server is a display. Use the right syntax :40 or HOSTNAME:40, not 40. X client and X server communicates with X11 protocol(over TCP or UDS), not nessacarily sockets because some platform doesn't have it. For linux, sockets or any file can't be owned by a process, linux doesn't have this concept.

    – 炸鱼薯条德里克
    27 mins ago



















  • unix.stackexchange.com/questions/503870/… So most phrases used in your question is meaningless. An X server is a display. Use the right syntax :40 or HOSTNAME:40, not 40. X client and X server communicates with X11 protocol(over TCP or UDS), not nessacarily sockets because some platform doesn't have it. For linux, sockets or any file can't be owned by a process, linux doesn't have this concept.

    – 炸鱼薯条德里克
    27 mins ago

















unix.stackexchange.com/questions/503870/… So most phrases used in your question is meaningless. An X server is a display. Use the right syntax :40 or HOSTNAME:40, not 40. X client and X server communicates with X11 protocol(over TCP or UDS), not nessacarily sockets because some platform doesn't have it. For linux, sockets or any file can't be owned by a process, linux doesn't have this concept.

– 炸鱼薯条德里克
27 mins ago





unix.stackexchange.com/questions/503870/… So most phrases used in your question is meaningless. An X server is a display. Use the right syntax :40 or HOSTNAME:40, not 40. X client and X server communicates with X11 protocol(over TCP or UDS), not nessacarily sockets because some platform doesn't have it. For linux, sockets or any file can't be owned by a process, linux doesn't have this concept.

– 炸鱼薯条德里克
27 mins ago










0






active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f505996%2fare-sockets-addressing-a-display-of-a-x-server-and-connected-to-or-created-by%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f505996%2fare-sockets-addressing-a-display-of-a-x-server-and-connected-to-or-created-by%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Loup dans la culture

How to solve the problem of ntp “Unable to contact time server” from KDE?

ASUS Zenbook UX433/UX333 — Configure Touchpad-embedded numpad on Linux