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
Message-ID:	<3DEE7DC4.9050500@etr-usa.com>
Date:	Wed, 04 Dec 2002 15:12:20 -0700
From:	Warren Young <warren AT etr-usa DOT com>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130
X-Accept-Language:	en-us, en
MIME-Version:	1.0
To:	Cygwin-L <cygwin AT cygwin DOT com>
Subject:	Re: Named Sockets
References:	<3DEE1D51 DOT 13221 DOT 6603430 AT localhost>
In-Reply-To:	<3DEE1D51.13221.6603430@localhost>
X-Note:	This E-mail was scanned by Declude JunkMail (www.declude.com) for spam.

Julian W H Osborne wrote:
> 
> I've just ported a server app which uses named sockets to cygwin.  

It might be simpler to port it to regular sockets, as there is a usable 
subset that works more or less the same on Windows and on POSIX-type 
systems (Cygwin, Linux, Unix....)  You can still make the socket 
available to programs running on the local machine only, by bind()ing it 
to IP address 127.0.0.1.

See the link below for more info on this.  All of the FAQ's examples can 
be compiled with Cygwin, except for the MFC-based ones.
-- 
= Winsock Programmer's FAQ: http://tangentsoft.net/wskfaq/


--
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 -