This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
Re: pipe replacement w/o TerminateThread
- From: Christopher Faylor <cgf at redhat dot com>
- To: cygwin-developers at cygwin dot com
- Date: Tue, 15 Apr 2003 11:23:34 -0400
- Subject: Re: pipe replacement w/o TerminateThread
- References: <3E9C113A.6010100@hekimian.com>
- Reply-to: cygwin-developers at cygwin dot com
On Tue, Apr 15, 2003 at 10:03:38AM -0400, Joe Buehler wrote:
>Christopher, I'm coding up an example for you, but I see two basic ways
>of doing this:
>
>1. Toss CreatePipe() and implement pipes with shared memory and semaphores.
So that native windows processes will never be able to use cygwin pipes.
>2. Use CreatePipe() but buffer data outside of the pipe, using a reader
> thread so the pipe never blocks.
Same problem with windows processes and all sorts of tricky inheritance
problems with exec/fork.
This "how do we deal with pipes" issue has been discussed since 1998
at the very least. There should be all sorts of words in the archives.
cgf