Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!aplcen!aplcomm!capd.jhuapl.edu!waltrip
From: waltrip@capd.jhuapl.edu
Newsgroups: comp.sys.next
Subject: Re: Mouse-X over the phone
Message-ID: <1991Mar15.120533.1@capd.jhuapl.edu>
Date: 15 Mar 91 17:05:33 GMT
References: <1991Mar14.204058.1474@wam.umd.edu>
Sender: news@aplcomm.JHUAPL.EDU
Organization: CAPVAX, JHU/APL
Lines: 46

In article <1991Mar14.204058.1474@wam.umd.edu>, mikec@wam.umd.edu (Michael D. 
Callaghan) writes:
>Now that I have Mouse-X up and running (thanks to the authors for a job
>well done), is there any way that I can interface my NeXT here at home
>with the VAXes at school? 
	In theory, yes, but the pieces aren't there.  You need a (supported)
	transport for shipping X protocol between the X clients and your
	Mouse-X server.  If the NeXT had DECnet, you could, of course, use
	that.  If your VAX has tcp/ip, there may be a supported mechanism
	for that as well depending on whose tcp/ip (I know Wollongong, TGV
	Multinet, CMU and DEC's UCX support DECwindows) but here's where all
	those discussions about SLIP or PPP for the NeXT hit home.  Even
	though your NeXT supports tcp/ip, it supports it only over Ethernet.
	If you had SLIP on the NeXT and SLIP support on the VAX (I don't
	know which implementations of tcp/ip on VMS support SLIP except that
	TGV Multinet does) then you run as desired (well, maybe...X likes
	transport bandwidth and it's likely to be painfully slow over a 9600
	baud line).
>
>Specifically, I'd like to call up the VAX, and run X programs on their
>machine. I can tell the VAX that I'm an xterm, and vi seems to work really
>well. However, if I try to run an X program, I get a message about not
>being able to open the display.
	If that were a tcp/ip link and you had logged on to your VAX via
	telnet, you would issue the DCL command
		$ set display/create/node=yourNeXTnodename/transport=???
	where ??? is furnished by the instructions for your VAX tcp/ip
	implementation on running DECwindows.
>
>I was once told that X only worked over an ethernet line. I would hate to
>find that that's true. 
	It's not true but might be fair to say that it doesn't work well
	over less than a 56Kbyte link (I have no firsthand experience with
	serial line operation...I am passing on what others have said but
	it may depend on what X clients you are running as to how satisfactory
	performance is...I hope to be able to find out firsthand someday
	when my NeXTstation arrives and after I have purchased coXist and that
	implementation of SLIP that was announced in this newsgroup recently).

	[...]

c.f.waltrip

Internet:  <waltrip@capsrv.jhuapl.edu>

Opinions expressed are my own.