The client-server terminology when referring to X (was: Remote X login)

From: Maxim Vexler (hq4ever_at_gmail.com)
Date: 10/31/05

  • Next message: Hugo Vanwoerkom: "Re: Sid, problems with 2.6.14" 
    Date: Mon, 31 Oct 2005 23:23:20 +0300
To: debian-user@lists.debian.org

    On 10/31/05, Jon Dowland <lists@alcopop.org> wrote:
    > On Mon, Oct 31, 2005 at 03:00:26PM -0000, marc wrote:
    > > Used on the client
    > ^^^^^^
    >
    > Beware confusing client and server when discussing X. In X parlance, the
    > server is your desktop and the machine with the applications on is the
    > client. This is because the X server is running on your desktop (or
    > laptop, or whatever).
    >

    Trying to format this into human understanding :

    The application has received some input, and now needs to respond with
    output - a drawing.
    The application (which is running on the remote machine) says "Hi, I
    need someone to do the drawing for me! That is why I am the CLIENT, I
    ask the server to draw my outer self. serve me! :)

    The X server (which is running on the local laptop) obeys the demands
    of the application and draws what was requested from him, that is why
    the laptop in question is the SERVER. He served the application and
    drew what was requested from him.

    The significant resource consumption in on the _client_ and NOT on the
    server as one would expect. That is because all the rendering, data
    structures, CPU calculation cycles, I/O and so on is done on the
    client. The server (in X terminology) only receives raw drawing data,
    using the mentioned XDMCP transmission, and those act's in a vary
    mature manner "He told me to, so I did it" :)

    Is my analogy correct ?

    /// Skipping the user interaction phase, in hope that someone could
    fill me in...
    If the laptop in the example is the server, and yet the user is
    obviously working on that laptop... How then does the application
    knows what to ask the server to drew next ? Who sends the input from
    the user back to the application so that it in turn could instruct the
    X server what to draw next ? ///

    Would love to read some clarification on this subject, as it is known
    to confuse a lot of (newbie) users like me. 

    --
Cheers,
Maxim Vexler (hq4ever).
Do u GNU ?
  • Next message: Hugo Vanwoerkom: "Re: Sid, problems with 2.6.14"

    Relevant Pages

    • Re: Unable to access local workstations from SBS 2003
      ... domain AT the client. ... I did focus on the DNS of the server as a possible issue. ... Relative to the "..computer name is not in Win2K3" I mean that the laptop ... >> I'm able to do just about anything from the laptop or any other workstation ...
      (microsoft.public.windows.server.sbs)
    • Re: What doesnt lend itself to OO?
      ... >> proxy and instructs the server to constuct the real object. ... rather than client code. ... If 'clock' is instantiated in the server, ... > for the server interface at the OOA level. ...
      (comp.object)
    • This is going straight to the pool room
      ... or not the client has privilege to do what they're trying to do, ... The server environment is this: ... 3GL User action Routines that Tier3 will execute on your behalf during the ... Routine Name: USER_INIT ...
      (comp.os.vms)
    • [Full-Disclosure] R: Full-Disclosure Digest, Vol 3, Issue 42
      ... Full-Disclosure Digest, Vol 3, Issue 42 ... SD Server 4.0.70 Directory Traversal Bug ... Arkeia Network Backup Client Remote Access ...
      (Full-Disclosure)
    • Re: Unable to access local workstations from SBS 2003
      ... Ensure there is no local HOSTS and LMHOSTS files on the client PCs ... Not sure why you would specify the UNC computer path - browse to the server, find a server share, right click 'Copy' ... Relative to the "..computer name is not in Win2K3" I mean that the laptop computer name, eg DCF9R51, is not part of the "Computers" in Active Directory. ... I'm able to do just about anything from the laptop or any other workstation on the domain: logon, WinExplore, delete but, evidently, not copy/move FROM the server. ...
      (microsoft.public.windows.server.sbs)