Message-ID: <002001c96462$6a46d790$4001a8c0@mycomputer>
From: "John Emmas" <johne53@tiscali.co.uk>
To: <cygwin@cygwin.com>
References: <005b01c96455$6c6bed60$4001a8c0@mycomputer> <2ca21dcc0812220903k38b8923v892f508b2ec55620@mail.gmail.com> <20081222172855.GB27364@ednor.casa.cgf.cx>
Subject: Re: Named pipes (blocking problem)
Date: Mon, 22 Dec 2008 18:23:40 -0000
MIME-Version: 1.0
Content-Type: text/plain; 	format=flowed; 	charset="iso-8859-1"; 	reply-type=original
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Note-from-DJ: This may be spam

Many thanks guys - the blocking pipes are being created with PIPE_WAIT and
without FILE_FLAG_OVERLAPPED and they successfully block if I build under
VC++ but not when I build under Cygwin.  I must confess, I don't understand
the subtle difference between asynchronous operation and nonblocking
operation but I'll see what I can find out from Google.


----- Original Message ----- 
From: "Christopher Faylor"
Sent: 22 December 2008 17:28
Subject: Re: Named pipes (blocking problem)
>
> If the OP is creating a pipe using CreateNamedPipe and then trying to
> somehow read it using Cygwin's I/O library then I wouldn't be surprised
> to see strange behavior.  Otherwise, Cygwin does not impose any strange
> limitations on CreateNamedPipe.
>
Thanks Christopher.  This is really at the heart of what I'm trying to find
out.  Does Cygwin implement its own versions of CreateNamedPipe() and
ReadFile() or does it simply link to the standard Windows versions?  If it
passes the calls over to Windows then I'm baffled about why I'm observing
different behaviour.

John

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/