Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!apple!snorkelwacker!bloom-beacon!houvmscc.iinus1.ibm.COM!rabbit
From: rabbit@houvmscc.iinus1.ibm.COM
Newsgroups: comp.windows.x
Subject: Display Sharing
Message-ID: <9010031802.AA18296@expo.lcs.mit.edu>
Date: 3 Oct 90 18:04:10 GMT
Sender: root@athena.mit.edu (Wizard A. Root)
Organization: The Internet
Lines: 37

From: zephyr.ens.tek.com!videovax!errolc@uunet.uu.net  (Errol Crary)
Organization: Tektronix TV Measurement Systems, Beaverton OR
Subject: Re: Display sharing

>>I am working as part of the design effort for the Mission Control
>>Center for Space Station Freedom.  We have a requirement for the
>>capability to share displays between consoles that are going to be a
>>variety of workstations of an unknown flavor running Xwindows.
>>
>It is difficult to understand the requirements you have. In X, the word
>are well defined; a display consists of a instance of the server, one o

Maybe I should give a scenario of what the users in our environment
want to be able to do.

1) A Flight Controller is looking at a window at his workstation
   watching a graphical representation of part of the telemetry
   downlink from the space station.
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.

   One of the main reasons for this capability is for training new
   Flight Controller.

   The capability to share displays should be a separate application
   and should not have to be custom code that needs to be included
   in each application or subsystem.

Bill Kossack