Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!uunet!island!hue
From: hue@island.uu.net (Jonathan Hue)
Newsgroups: comp.sys.next
Subject: Re: NeXT Window server access from other nonNeXT systems...
Message-ID: <2267@island.uu.net>
Date: 5 Dec 90 17:29:42 GMT
References: <1990Nov29.221957.781@gacvx2.gac.edu>
Organization: Island Graphics Corp., San Rafael, CA
Lines: 29

In article <1990Nov29.221957.781@gacvx2.gac.edu>, dan@gacvx2.gac.edu writes:
> While writing this, I just had an idea for a simple sounding daemon that would
> listen on a TCP port.  A program on a remote host could open a TCP connection
> to that port and write Display Postscript(tm) to the NeXT, the daemon on the

I don't know if this is still true, but you used to be able to telnet to the
window server and type PostScript at it.  Look in /etc/services for something
like:

pswm	xxx/tcp

and then type "telnet some_next_box xxx".  You should then be able to send
PostScript to the window server.  As I recall, you had to type "flush" to
get it to print the results of operators like "pstack"

> NeXT would pop open the window and display the image.  Some method of sending
> NeXT events to the window back to the remote host would be cool.  Now if I just
> had time to program...

If you had Mach message passing and the net message server running on the
remote host you could do this.  But then you'd have to do a lot of the work
yourself that the DPS client library and Appkit does for you on the NeXT.


--
Only in Marin:  Sign next to Sony waterproof cordless phone in department
store calls it "Marin Hot Tub model"

Jonathan Hue	Island Graphics Corp.	uunet!island!hue   hue@island.com