Path: utzoo!attcan!uunet!snorkelwacker!bloom-beacon!AIS1.BAL.MMC.COM!wicks
From: wicks@AIS1.BAL.MMC.COM (Anthony B. Wicks)
Newsgroups: comp.windows.x
Subject: Display Sharing
Message-ID: <9010041330.AA09528@ais1.bal.mmc.com>
Date: 4 Oct 90 13:30:13 GMT
References: <9010031802.AA18296@expo.lcs.mit.edu>
Sender: root@athena.mit.edu (Wizard A. Root)
Organization: The Internet
Lines: 37


   Date: Wed, 3 Oct 90 13:04:10 CDT
   From: rabbit@houvmscc.iinus1.ibm.com

   From: zephyr.ens.tek.com!videovax!errolc@uunet.uu.net  (Errol Crary)
   Organization: Tektronix TV Measurement Systems, Beaverton OR
   Subject: Re: Display sharing
   ...
   2) An event takes place that he either doesn't understand or needs
      to have another controller look at (or maybe a number of people
      are interested in and ask to look at).  As Flight Controllers
      may be in separate rooms.  It would be difficult for one to
      get up and walk over to the other workstation.  Remote connections
      to workstations will not be permitted because of a number
      reasons one of which is security.
   3) There is a need to be able to select and distribute the content
      of that window (we call them screens or displays) so they can
      see what the original Flight Controller is doing.

Requirements 2 & 3 seem to be at odds.  Either the systems are connected or
they are not.  To be able to send information from one system to another
implies a connetion of some type.  For security purposes you may need to
use two displays at the remote location -- one for user interaction, and
one for dumping information.  This dumping terminal could be some kind of
xterminal which only has a mouse, allowing the user to interact with the
window manager (to close/iconify windows), but not enter data.  The Flight
Controller station would have some variant of xwd, modified to only dump
windows with prespecified names (to meet security) to the remote dumping
terminal.  This would meet your "separate application" requirment, and
seems like it could be done with very little custom code.  Unforetunately
using xwd as the basis would provide the dumping terminal with static
displays only, but this is a starting point. HOWEVER, there must be a
connection between the remote "dumping" X terminal and the Flight
Controller's computer.


____________________________<Anthony B. Wicks, Jr>______________________________