Path: utzoo!attcan!uunet!snorkelwacker!bloom-beacon!houvmscc.iinus1.ibm.COM!rabbit
From: rabbit@houvmscc.iinus1.ibm.COM
Newsgroups: comp.windows.x
Subject: Display Sharing
Message-ID: <9010061852.AA11826@expo.lcs.mit.edu>
Date: 6 Oct 90 18:55:03 GMT
Sender: root@athena.mit.edu (Wizard A. Root)
Organization: The Internet
Lines: 40

In a previous note I said

    ...
>   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.

Errol Crary replied to me

>Requirements 2 & 3 seem to be at odds.  Either the systems are connected or
>they are not.  To be able to send information.............

Others have given similar comments with my statement.  :-)

Don't worry because there are a couple of people here that have the job of
designing the security system for the network.  One of the big problems is
how do you build security into the system to satisfy security requirements
that originated when all of the Mission Control software ran on a mainframe.

We are trying to build a distributed LAN solution with numerous
workstations each running parts of various subsystems and maintain some
of the same security that was available when everyone was connected to one
mainframe and was located in one room.

Needless to say there will be a piece of code or a person somewhere with a
list of who gets to look at what displays (all displays will be known by the
system).  There will also probably be strict rules as to how many displays
can be distributed because even though we are talking of a system with
multiple FDDI LANS with the amount of data and the time critical nature
of the data it would be easy to overload the network with shared displays.

Working on weekends is no fun.
Bill Kossack