Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.ARPA
Path: utzoo!watmath!clyde!cbosgd!ucbvax!csnet-relay.arpa!NEVILLE%umass-cs.csnet
From: NEVILLE%umass-cs.csnet@CSNET-RELAY.ARPA
Newsgroups: fa.info-vax
Subject: RE: Broadcasting vs PASSALL
Message-ID: <8509111420.AA16748@UCB-VAX.ARPA>
Date: Tue, 10-Sep-85 09:38:00 EDT
Article-I.D.: UCB-VAX.8509111420.AA16748
Posted: Tue Sep 10 09:38:00 1985
Date-Received: Thu, 12-Sep-85 10:24:37 EDT
Sender: daemon@ucbvax.ARPA
Reply-To: info-vax@ucb-vax.arpa
Organization: The ARPA Internet
Lines: 13

Yes, using the new PASTHRU setting does solve much of the problem, although
sometimes i'd rather have *all* input available instead of losing ^S, ^Q to
flow control.  Usually i'd rather have flow control.  What i should have
emphasized is that the (BRDCSTMBX) method i described allows you to gain
control over how the broadcast messages are handled.  You can choose to
scribble them on the display just like the TTDRIVER, store them up for
display on program exit,  issue them into a special "broadcast" window, or
whatever.  You can even use it to screen your PHONE calls!  Note that it
will also work from another process in your session.  i sometimes spawn
a background process for the express purpose of handling broadcast messages.

						Neville Newman
						neville@umass-cs  (CSnet)