🚀 go-pugleaf

In article <werFEuu00WAvQ1gMJX@andrew.cmu.edu>  writes:
> 
> 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

How about an app that uses distributed objects.  One program would be  
autolaunched by every user and then connect to the server app.  Whenever  
the network needs to be shutdown the server just sends a message to the  
client apps telling them to NXRunAlertPanel. Sounds pretty simple, but I  
haven't looked at distributed objects for very long.

--
Paul           (NeXTmail preferred)

Anyone who is capable of getting themselves made President should on no  
account be allowed to do the job.
-- Douglas Adams, "The Hitchhiker's Guide to the Galaxy"