pipe replacement w/o TerminateThread

Christopher Faylor cgf@redhat.com
Tue Apr 15 15:23:00 GMT 2003

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.


More information about the Cygwin-developers mailing list