Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!pasteur!ucbvax!decwrl!shelby!polya!ali
From: ali@polya.Stanford.EDU (Ali T. Ozer)
Newsgroups: comp.sys.next
Subject: Re: -host option (was Re: NeXT alternatives)
Message-ID: <8363@polya.Stanford.EDU>
Date: 11 Apr 89 08:30:13 GMT
References: <12192@reed.UUCP> <245300010@uxe.cso.uiuc.edu> <688@garcon.cso.uiuc.edu> <BOB.89Mar30124012@allosaur.cis.ohio-state.edu> <41358@tut.cis.ohio-state.edu> <8277@polya.Stanford.EDU> <4683@umd5.umd.edu>
Sender: Ali T. Ozer <ali@polya.Stanford.EDU>
Reply-To: aozer@NeXT.com (Ali Ozer)
Distribution: usa
Organization: .
Lines: 22

In article <4683@umd5.umd.edu> feldman@umd5.umd.edu (Mark Feldman) writes:
>
>The problems with the -host option that appear immediately are:
>
>	While the visual part of the interface appears on the target
>	machine, sounds are produced on the source machine (I assume that
>	all DSP-related action run on the source machine).
>
0.9 addresses this problem somewhat by providing the server with means to
generate sounds (PostScript operator to generate sounds, anyone?). This
operator is really meant for beeps, sounds tied to buttons, and other short
sound segments... Under 0.9 you do not get the nice features of the soundkit 
when you generate sounds through the window server.

>	Using the -host option, anyone can put windows on YOUR NeXT.  There
>	doesn't appear to be an equivalent to the X xhost command.
>
In 0.9 a user can prevent other machines from putting windows on his/her
machine. This is done by specifying whether you want your window server to
be "public" or not.

Ali