From: Todd on
Hi All,

I am confused. When running "X" windows, is the
terminology reversed? By chance is the computer
hosting the applications called the client and
the remote computer viewing the applications called
the server? Is so, why is this?

Many thanks,
-T
From: Grant Edwards on
On 2010-01-27, Todd <todd(a)invalid.com> wrote:

> I am confused. When running "X" windows, is the
> terminology reversed?

Nope. The program requesting the services is the client, the
program providing the services is the server.

> By chance is the computer hosting the applications called the
> client and the remote computer viewing the applications called
> the server? Is so, why is this?

See above. The "service" consists of drawing on the screen.

Which program is doing the actual drawing? That's the server.

Which program is requesting that things be drawn? That's the
client.

Client/server nomenclature is about who's requesting the
service and who's providing the service. It's got nothing to
do with geographic location.

--
Grant Edwards grante Yow! if it GLISTENS,
at gobble it!!
visi.com
From: Stan Bischof on
Todd <todd(a)invalid.com> wrote:
> Hi All,
>
> I am confused. When running "X" windows, is the
> terminology reversed? By chance is the computer
> hosting the applications called the client and
> the remote computer viewing the applications called
> the server? Is so, why is this?
>

yes- it is backwards

the SERVER is where the display is ( typically your local system )
the CLIENT is where the bits are running ( typically the server )

It pretty much makes sense if you understand how X works-
in essence "clients" request graphics and hence are
served by the "server" which provides the resources
but is of course unfortunate since it is backwards!

Stan
From: Todd on
On 01/27/2010 12:08 PM, Grant Edwards wrote:
> On 2010-01-27, Todd<todd(a)invalid.com> wrote:
>
>> I am confused. When running "X" windows, is the
>> terminology reversed?
>
> Nope. The program requesting the services is the client, the
> program providing the services is the server.
>
>> By chance is the computer hosting the applications called the
>> client and the remote computer viewing the applications called
>> the server? Is so, why is this?
>
> See above. The "service" consists of drawing on the screen.
>
> Which program is doing the actual drawing? That's the server.
>
> Which program is requesting that things be drawn? That's the
> client.
>
> Client/server nomenclature is about who's requesting the
> service and who's providing the service. It's got nothing to
> do with geographic location.
>

Okay. I think I understand. If I rdesktop into a remote machine,
the local machine is the server as it is doing the actual drawing
on the screen. The remote machine with the application on it
is the client as it is requesting the drawing. It all seems
backwards to me, but as long as I understand what is going on ...

So, if I want to run an "X" windows desktop from a Linux
server on a M$ Windows machine, I run an "X" server on the M$ machine.
In this respect, I am use to M$ Terminal Services, where the
requesting machine is called the server and the drawing machine
is called the client. My brain hurts.

Many thanks,
-T
From: David W. Hodgins on
On Wed, 27 Jan 2010 14:33:35 -0500, Todd <todd(a)invalid.com> wrote:

> I am confused. When running "X" windows, is the
> terminology reversed? By chance is the computer
> hosting the applications called the client and
> the remote computer viewing the applications called
> the server? Is so, why is this?

I connect to another computer over the network using ssh. Start
an application such as gkrellm. It's running on the remote
computer, but it's display output is shown on my computer.

The server, is the X application on my computer. The client
is the gkrellm application on the remote computer.

Regards, Dave Hodgins

--
Change nomail.afraid.org to ody.ca to reply by email.
(nomail.afraid.org has been set up specifically for
use in usenet. Feel free to use it yourself.)