Re: Info on "Can't open display"

["Robert Collins" <robert dot collins at itdomain dot com dot au>]

----- Original Message -----
From: "Suhaib Siddiqi" <ssiddiqi@inspirepharm.com>
To: "'Robert Collins'" <robert.collins@itdomain.com.au>;
<cygwin-xfree@cygwin.com>
Sent: Saturday, June 16, 2001 11:28 AM
Subject: RE: Info on "Can't open display"


>
>
> > Suhaib made a _very_ good point. X (may be)/(is) using AF_UNIX
sockets
>
> Actually under Cygwin it is using AF_UNIX.  For Win32-X11 project I
used
> Only Microsoft Winsock32, which most of the commercial X-servers do.
> Therefore I asked the Aventail users if they can test some clients,
e.g.
> Xclock, and oclock etc from win32-x11 project.  I am working on a
binary
> release which will use winsock32.  Let's see if that will help.
>
> Suhaib

You will lose fork() support for sockets if you use winsock32 directly.
I'm much more keen on identifying why the problem occurs - we can
probably solve it quickly inside cygwin1.dll once we know that.

Rob

>
> > for local connections. Cygwin1.dll emulates such sockets using
normal
> > win32 sockets and a file on disk. If thats the case any win32 only
> > program is not a valid example of a working tool. What would be a
valid
> > comparison is a test client-server package that use AF_UNIX
sockets -
> > say CORBA based or something similar.
>
>