Path: utzoo!attcan!telly!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!cs.utexas.edu!uunet!orca!undies!pmartz
From: pmartz@undies.dsd.es.com (Paul Martz)
Newsgroups: comp.windows.x
Subject: Re: host:display.screen
Message-ID: <1991Feb5.234933.1312@dsd.es.com>
Date: 5 Feb 91 23:49:33 GMT
References: <9102041741.AA03063@TERRE.matra-espace.fr>
Sender: news@dsd.es.com
Reply-To: pmartz@undies.dsd.es.com (Paul Martz)
Organization: Evans & Sutherland Computer Corp., Salt Lake City, UT
Lines: 22
Nntp-Posting-Host: 130.187.85.56

In article <9102041741.AA03063@TERRE.matra-espace.fr>, paulet@terre.matra-espace.fr (Pascal PAULET 6109 FAMI2) writes:
> can you tell me if anybody knows implementations where a single host
> supports multiple displays (not screens!). I know that this is
> theoritically possible thanks to the host:display.screen format
> of the XOpenDisplay argument.
> 
> Thank you.
> 
> Pascal.

You can do this on most any X implementations by bringing up X
and then bringing up xscope, which acts as both a client to the
first server and a server unto itself. Subsequent clients can
display on either host:0.screen (the X server) or host:1.screen
(xscope).

(xscope is useful for debugging at the protocol layer; there
are other tools which work in similar fashions. I believe it's
in the contrib directory of the X source tree.)
-- 

   -paul	pmartz@dsd.es.com