🚀 go-pugleaf

Excerpts from mail: 15-Oct-92 Re: How to message network .. by David Apfelbaum 
> For the benefit of you folks that are not on AFS, the X version (Andrew
> implementation) of zephyr has  a source tree >8.6 Megabytes.  Conversion
> to NeXTStep may be worthwhile, but will most likely be extremely
> non-trivial.

9 Megs???  What in god's name is in there?  Actually, I can believe that
the multiple font support, et al. would take some space.  It shouldn't
take too much effort to support a text-only version that'd bring up an
alert panel.

>  
> Now, why can we simply write a 10 line program that uses NXRunAlertPanel
> to run a alert-panel with an OK button, and then arrange to have it run
> remotely on whatever machine you wish it run on...  (Net-gurus, is there
> any way to have inetd run it on demand?  Or would we need a daemon
> process on each machine?)  (For that matter, will it (the daemon or
> whatever process) need to be owned by the current user to access the
> workspace?)
>  
>  
>                 -David Apfelbaum
>                  da0g+@andrew.cmu.edu

Well, the standard way that async net connections are made is by
defining a port number that the inetd listens on, and starts up a daemon
to service the request.  For zephyr at CMU (from /etc/services):

zephyr-clt      2103/udp
zephyr-hm       2104/udp

So the answer is yes.  At CMU, the user has to start up his own zephyr
daemon, but it could be done from /etc/inetd.conf as well.  If I have a
large amount of free time, I'll look into whether I can tackle the
problem.

-Chuck


+---------------------------------------------+ 
|  Charles William Swiger -- CMU sucks rocks  | "The television screen is the
|   AMS & normal mail: cs4w+@andrew.cmu.edu   | retina of the mind's eye."
|    NeXTmail: <temporarily out of order>     |           
+---------------------------------------------+            --Videodrome