httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Trawick <traw...@ibm.net>
Subject Re: [PATCH] Re: extra syscalls related to ap_create_pipe()
Date Mon, 19 Jun 2000 13:59:28 GMT
Another reason not to unconditionally make pipes non-blocking:

  Win9x can't do non-blocking pipes...

Currently, with OS/2*, Unix, and I guess BeOS, ap_create_pipe()
returns handles which work non-blocking.

With WinNT you get blocking handles, but this is easily remedied.

With Win9x, there is no remedy AFAIK other than reimplementing pipes
from the ground up.  I think Win9x has the old OS/2 1.x (non-server
limitation of not being able to *create* a named pipe; thus that
avenue is probably blocked.

*I guess there is magic that makes the write output handle (created
by DosOpen()) non-blocking by virtue of the fact that the pipe was
created non-blocking.  Not real sure...  The input handle is
definitely non-blocking.

-- 
Jeff Trawick | trawick@ibm.net | PGP public key at web site:
     http://www.geocities.com/SiliconValley/Park/9289/
          Born in Roswell... married an alien...

Mime
View raw message