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 Date: Wed, 4 Dec 2002 16:07:04 +0000 (GMT Standard Time) From: Max Bowsher To: Julian W H Osborne cc: cygwin@cygwin.com Subject: Re: Named Sockets In-Reply-To: <3DEE1D51.13221.6603430@localhost> Message-ID: X-X-Sender: mob22@imap.hermes.cam.ac.uk MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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/