Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <3DEE7DC4.9050500@etr-usa.com> Date: Wed, 04 Dec 2002 15:12:20 -0700 From: Warren Young 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 Subject: Re: Named Sockets References: <3DEE1D51.13221.6603430@localhost> In-Reply-To: <3DEE1D51.13221.6603430@localhost> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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/