Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!snorkelwacker!bloom-beacon!SHAMASH.MCRCIM.MCGILL.EDU!mouse
From: mouse@SHAMASH.MCRCIM.MCGILL.EDU (der Mouse)
Newsgroups: comp.windows.x
Subject: Re:  Questions (rlogin vs remote xterm)
Message-ID: <9006021303.AA04433@shamash.McRCIM.McGill.EDU>
Date: 2 Jun 90 13:03:38 GMT
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 35

> 2. The power of X window is "network transparent windowing..." right?

Well, that's one of its strengths.

>    So, I tried like: 
> 	xhost doItThere
> 	rsh doItThere "setenv DISPLAY showMeHere; do it"
>    It was ok, but is this right way?

It's not unreasonable.

>    Then what is difference with rlogging to the other machine and
>    execute it inside the popped up shell window?

The major difference is where it places the load.

In my experience...suppose machine A is running the X server and
machine B is where I want my shell to be.

Way 1	A% xterm -e rlogin B
Way 2	A% rsh B xterm -display A:0

(No nitpicking please, those are typed `off the top of my head'.)

I find that way 1 puts less of a load on B than 2 does.  To be more
precise, when B is an overloaded or otherwise slow machine, way 1
produces noticeably better response.

If you're using a standard rlogin, way 1 has the disadvantage that the
rlogin escape character is active.

					der Mouse

			old: mcgill-vision!mouse
			new: mouse@larry.mcrcim.mcgill.edu