Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 56799 invoked by uid 500); 21 Jun 2000 02:05:14 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk X-No-Archive: yes Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 56773 invoked from network); 21 Jun 2000 02:05:12 -0000 X-Authentication-Warning: koj.rkbloom.net: rbb owned process doing -bs Date: Tue, 20 Jun 2000 19:05:37 -0700 (PDT) From: rbb@covalent.net X-Sender: rbb@koj.rkbloom.net To: "new-httpd@apache.org" , Brian Havard Subject: Re: cvs commit: apache-2.0/src/main http_log.c In-Reply-To: <200006210106.LAA07176@silk.apana.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N > > OS/2: > > > > ap_set_pipe_timeout() with timeout value > 0: The code didn't play with > > the blocking state before and it doesn't still. I did add logic for special > > timeout values 0 and -1 to play with the blocking state. > > > > ap_create_pipe(): old logic didn't do anything with the blocking state > > of the second handle; it still doesn't; hopefully it is blocking > > Good try but this won't work. The pipe must always be created non-blocking > (else the DosConnectNPipe() blocks forever) & can stay that way. OS/2 > allows attaching an event semaphore to the pipe which is triggered when > data is available. The parameters to the call to wait on that semaphore > determine the block/non-block/timeout behaviour. Can we just create it non-blocking and use a -1 timeout value on OS/2? Ryan _______________________________________________________________________________ Ryan Bloom rbb@apache.org 406 29th St. San Francisco, CA 94131 -------------------------------------------------------------------------------