Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Sun, 25 Mar 2001 17:06:38 -0500 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: setup will have to wait :[ Message-ID: <20010325170638.A897@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <001b01c0b397$2d1ca720$0200a8c0 AT lifelesswks> <1783665564 DOT 20010323155742 AT logos-m DOT ru> <000501c0b3e9$7fa3d890$0200a8c0 AT lifelesswks> <183264218826 DOT 20010325190658 AT logos-m DOT ru> <005b01c0b575$112ff2d0$0200a8c0 AT lifelesswks> <20010325165305 DOT A32188 AT redhat DOT com> <010c01c0b576$a93cdb00$0200a8c0 AT lifelesswks> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <010c01c0b576$a93cdb00$0200a8c0@lifelesswks>; from robert.collins@itdomain.com.au on Mon, Mar 26, 2001 at 07:57:59AM +1000 On Mon, Mar 26, 2001 at 07:57:59AM +1000, Robert Collins wrote: >> Cygwin doesn't implement named pipes. Isn't a fifo == a named pipe >> anyway? > >Yes. I'm looking into the behaviour in more detail defore I cut code, >but yes. My planned implementation is a shared memory region that lists >the named pipes open on the system (maintained automagically via any >open cygwin process), a couple of waitable objects (probably 1 semaphore >and 1 event) per open fifo, and finally a (pick a good buffer size) >shared memory region for doing the actual data transfer. How about just using actual pipes? You could duplicate handles between processes. I don't know if pipe semantics are the same as fifos but I suspect that they are. cgf