Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!mouse
From: mouse@thunder.mcrcim.mcgill.edu (der Mouse)
Newsgroups: comp.windows.x
Subject: Re: How do *you* handle multiple displays?
Message-ID: <1991Jun29.114322.19963@thunder.mcrcim.mcgill.edu>
Date: 29 Jun 91 11:43:22 GMT
References: <14246@maslow.ptolemy-ri.arc.nasa.gov> <14258@ptolemy-ri.arc.nasa.gov> <1991Jun28.132932.21795@crl.dec.com>
Organization: McGill Research Centre for Intelligent Machines
Lines: 24

In article <1991Jun28.132932.21795@crl.dec.com>, jg@crl.dec.com (Jim Gettys) writes:
> In article <1991Jun28.131900.28715@thunder.mcrcim.mcgill.edu>, mouse@thunder.mcrcim.mcgill.edu (der Mouse) writes:
>> [The Xlib document] says that "On a POSIX system, this
>> [XConnectionNumber] is the file descriptor of the connection.",

>> (What about connections that don't have file descriptors?  Does the
>> above forbid such things?  I don't know, but wouldn't mind finding
>> out.)

> It doesn't forbid returning other useful information on other than
> Unix environments; the specification is deliberately silent to allow
> for such use.

I didn't say "other than Unix"; I said "don't have file descriptors".
There are plenty of ways the connection could be implemented on UNIX
that don't involve file descriptors, and some of them are plausible -
for example, buffers in a shared memory segment, with semaphores used
to tell the other end to look at the buffer.

					der Mouse

			old: mcgill-vision!mouse
			new: mouse@larry.mcrcim.mcgill.edu