Path: utzoo!attcan!uunet!samsung!zaphod.mps.ohio-state.edu!uwm.edu!dogie.macc.wisc.edu!decwrl!decwrl!wsl.dec.com!klee
From: klee@wsl.dec.com (Ken Lee)
Newsgroups: comp.windows.x
Subject: Re: Multiple screen/display applications
Message-ID: <4672@bacchus.dec.com>
Date: 3 Jun 90 22:41:54 GMT
References: <9006012334.AA02822@prefect.es.llnl.gov>
Sender: news@decwrl.dec.com
Reply-To: klee@wsl.dec.com
Organization: DEC Western Software Laboratory
Lines: 26

In article <9006012334.AA02822@prefect.es.llnl.gov>,
rms@prefect.es.llnl.GOV (Robert M. Searfus) writes:
> I would be very interested in hearing
> from anyone who has used (or is planning to use) X in an application
> requiring more that one physical display monitor.

There are a couple of different ways to do this:

1.  One CPU with 2 monitors.  DEC sells some machines like this.  I'm
sure other vendors do, too.  With this configuration, one X server
manages both displays, considering them to be separate screens.  The
application interacts with either screen through a single connection to
that X server.

2.  Two CPUs, each with 1 monitor.  This configuration is more
expensive, but more flexible.  Since each CPU will have it's own X
server, the application must create and manage separate connections to
each.  Since X supports networking, this is pretty simple to do.

Note:  I use the term CPU for lack of a better term.  It can be a
workstation, X terminal, or whatever.

Ken Lee
DEC Western Software Laboratory, Palo Alto, Calif.
Internet: klee@wsl.dec.com
uucp: uunet!decwrl!klee