Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Wed, 4 Dec 2002 16:07:04 +0000 (GMT Standard Time)
From:	Max Bowsher <maxb AT ukf DOT net>
To:	Julian W H Osborne <josborne AT imsmaxims DOT com>
cc:	cygwin AT cygwin DOT com
Subject:	Re: Named Sockets
In-Reply-To:	<3DEE1D51.13221.6603430@localhost>
Message-ID:	<Pine.WNT.4.44.0212041603470.1152-100000@pc361.nmus.pwf.cam.ac.uk>
X-X-Sender:	mob22 AT imap DOT hermes DOT cam DOT ac DOT uk
MIME-Version:	1.0

On Wed, 4 Dec 2002, Julian W H Osborne wrote:
JWHO> I've just ported a server app which uses named sockets to cygwin.
JWHO> Everything works fine within the cygwin environment.
JWHO> What I can't figure out is how
JWHO> to make a windows app access this named socket.

I assume by "named socket", you mean "unix domain socket" ?

IIRC, you simply can't get a non-Cygwin app to talk to a Cygwin unix
socket. They are just too alien to Windows, that Cygwin needs to mediate
both ends of the connection to get them to work.

Max.



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -