X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <2ca21dcc0812220903k38b8923v892f508b2ec55620@mail.gmail.com> Date: Mon, 22 Dec 2008 17:03:02 +0000 From: "Dave Korn" To: cygwin@cygwin.com Subject: Re: Named pipes (blocking problem) In-Reply-To: <005b01c96455$6c6bed60$4001a8c0@mycomputer> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <005b01c96455$6c6bed60$4001a8c0@mycomputer> Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 John Emmas wrote: > I'm trying to build a program that implements inter-process communication > using named pipes. Because the code needs to also work under Windows > (MSVC++) it uses CreateNamedPipe(...) to create the pipes (described here):- > > http://msdn.microsoft.com/en-us/library/aa365150(VS.85).aspx > > If I understand the description, it seems that the created pipe can either > be blocking or nonblocking depending on whether the flag > FILE_FLAG_OVERLAPPED is specified at creation time. Nope. Overlapped and blocking are slightly different concepts; overlapped basically means "enabled for asynchronous I/O". What you're looking for is PIPE_WAIT/_NOWAIT, further down the same page. cheers, DaveK -- 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/