Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!hplabs!well!pokey
From: pokey@well.UUCP (Jef Poskanzer)
Newsgroups: comp.windows.x
Subject: Re: unix:0
Message-ID: <5320@well.UUCP>
Date: 27 Feb 88 19:15:25 GMT
References: <1061@pasteur.Berkeley.Edu>
Organization: Paratheo-Anametamystikhood Of Eris Esoteric, Ada Lovelace Cabal
Lines: 25

In the referenced message, leres@ucbarpa.Berkeley.EDU (Captain Happy) wrote:
}You can certainly use "localhost:0" instead of "unix:0", but this will
}cause you to use an internet domain socket instead of a Unix domain
}socket to talk to the X server. And an internet socket to localhost
}isn't always as fast as a Unix domain socket.

I think you misunderstood what I did.  I hacked the X server so that
"localhost:0" did what "unix:0" normally does: used the Unix domain on
systems that support Unix domain.  And on SysV, all that code was
ifdef'ed out, so the same DISPLAY string got me an Internet socket.

}A better solution is to
}make "unix:0" mean "localhost:0" on systems that don't have Unix domain
}sockets.

This will work too.  But if you do it this way, you can't connect to
a host named "unix", as Phildo pointed out.  If you do it my way, the
only capability you lose is getting an Internet domain socket to
localhost when a superior Unix domain socket is available.  A smaller
price, I think.
---
Jef

              Jef Poskanzer   jef@lbl-rtsg.arpa   ...well!pokey
           "A man's got to know his limitations." -- Harry Callahan