bob@cis.ohio-state.edu (Bob Sutterfield) (12/31/88)
In article <414@ho7cad.ATT.COM> dean@ho7cad.ATT.COM (Dean S Jones) writes: >I need to ``duplicate'' the windows of our CAD package on the console >of another workstation. It looks as if the easiest approach is to run >the software on both workstations, and transmit events across a >network ( TCP/IP ) to the other workstation, where they get read by >an ``event reader'' and posted to the window of the running program. Congratulations - you've just invented an application-specific window system protocol :-) >We are using Sun 3's w/ Sunview 1.2. The use of a kernel-based window system would make this quite more difficult than it has to be, and far less general and portable. There's a mailing list called "sharedx@itsgw.rpi.edu" that discusses the issues involved in doing just what you're attempting to do. The use of a server-based window system eases and clarifies a lot of the protocol layering problems. That particular list (which, alas, has been dormant since 18 Oct) is concerned with X. Other work has been done in the Xerox world. I don't know of any work in the NeWS world, but the event structure could be hooked into similarly to the way that the 1.1 journaling works, and the events shipped hither and yon as update notices.
roberts%studguppy@lanl.gov (Doug Roberts) (01/04/89)
dean@ho7cad.ATT.COM (D.JONES): > I need to ``duplicate'' the windows of our CAD package on the console of > another workstation.... How about something a bit simpler: the following shell script (name it screen-copy)? #! /bin/sh # for i do while true do screendump -e | rsh $1 screenload sleep $2 done Ex: screen-copy dest-host-name 5 will do a screendump off of your host every 5 seconds and screenload it on to the target host. --Doug Douglas Roberts Los Alamos National Laboratory (505)667-4569 dzzr@lanl.gov