Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uunet!brunix!rca From: rca@cs.brown.edu (Ronald C.F. Antony) Newsgroups: comp.sys.next Subject: Re: Public {window,sound} server Message-ID: <59160@brunix.UUCP> Date: 11 Dec 90 20:51:57 GMT References: Sender: news@brunix.UUCP Reply-To: rca@cs.brown.edu (Ronald C.F. Antony) Organization: Brown University Department of Computer Science Lines: 20 When it comes to limiting access to the window server and the sound server there are a couple of things that need urgently to be changed. e.g. if you want to write a server application that is constantly running and provides services to a net of NeXT machines and needs access to the screen, you are screwed. I don't see why we cant go the good old unix way: create a device. e.g. /dev/winserv and /dev/sndserv that are chown'ed to the user at login and back to root at logout. These devices could have group assignments such that other applications that were installed by trusted staff for this purpose, can access the device in any case by default. In addition the user could set the permissions analog to regular file permissions in preferences. So where is the big problem with that? Ronald ------------------------------------------------------------------------------ "The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man." G.B. Shaw | rca@cs.brown.edu or antony@browncog.bitnet