Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!samsung!uakari.primate.wisc.edu!uwm.edu!rpi!image.soe.clarkson.edu!sunybcs!haozhou
From: haozhou@acsu.Buffalo.EDU (hao zhou)
Newsgroups: comp.windows.x
Subject: Re: client/server?
Keywords: X server
Message-ID: <14502@eerie.acsu.Buffalo.EDU>
Date: 10 Dec 89 15:38:05 GMT
References: <544@kunivv1.sci.kun.nl> <3245@ibmpa.UUCP> <10719@fs2.NISC.SRI.COM>
Sender: nobody@acsu.buffalo.edu
Reply-To: haozhou@autarch.acsu.buffalo.edu (hao zhou)
Distribution: comp.windows.x
Organization: Suny at Buffalo
Lines: 40

In article <10719@fs2.NISC.SRI.COM> cwilson@NISC.SRI.COM (Chan Wilson) writes:
>
>Is it possible to do the following:
>
>Log into local (slow) workstation.
>rlogin over to one of the fast machines
>Start X over on my workstation.
>

i don't think you can do this. 
one major difference of X to the other window systems is that display power 
and computational power are separate on different machines. X server (partially
including window manager) is running on your local machine managing i/o and
display of each window. Meanwhile X clients are running on a remote host.

>Reading the X man pages, this appears easily done.  Guess what?  I can't
>do it.  I either bring up X on the fast machine, using it's display;

if you rlogin on a remote host, you can't take any advantage of your local
machine since it becomes a regular terminal. in the other words, you won't
be able to have your local machine display windows.

>bring up X on the slow machine, using it's display, or bring up a
>non-working version of X on the fast machine.  
>

the correct way to do this is use a local *slow* machine to bring up window
while using a remote *fast* machine to run x clients or other applications.



	hao


Hao Zhou                 { Dept of Math, SUNY at Buffalo }
haozhou@sun.acsu.buffalo.edu
V092R9AZ@UBVMS.BITNET 
Hao Zhou                 { Dept of Math, SUNY at Buffalo }
haozhou@sun.acsu.buffalo.edu
V092R9AZ@UBVMS.BITNET