Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 21246 invoked by uid 6000); 21 Aug 1998 03:15:10 -0000 Received: (qmail 21236 invoked from network); 21 Aug 1998 03:15:08 -0000 Received: from unknown (HELO mail3.bellglobal.com) (198.235.216.132) by taz.hyperreal.org with SMTP; 21 Aug 1998 03:15:08 -0000 Received: from helium.jetpen.com ([207.164.141.23]) by mail3.bellglobal.com (Netscape Mail Server v2.02) with SMTP id AAA12662; Thu, 20 Aug 1998 23:13:05 -0400 Date: Thu, 20 Aug 1998 23:16:31 -0400 (Eastern Daylight Time) From: rasmus@lerdorf.on.ca (Rasmus Lerdorf) To: GodPerl Mailing List cc: new-httpd@apache.org Subject: Re: Spinning httpds - One Solution In-Reply-To: Message-ID: X-X-Sender: rasmus@imap3.bellglobal.com MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org > r->connection->aborted is only set by Apache after a a soft timeout. > Well, I'll ignore other situations. > > If the client just closes a connection, r->connection->aborted won't get > set. Well, that isn't true. Since the same code gets called on a timeout > then r->connection->aborted will actually get set if you get a SIGPIPE if > you are in a soft timeout, but not if you are in a hard timeout even if > the timeout has nothing to do with the connection being aborted. > > Why? Haven't a clue, you would have to ask someone who has a clue. But > you should listen to the return value from rwrite. Aha! That answers a long outstanding headscratcher for me. Is there a good reason for r->connection->aborted not getting set if a client closes the connection irregardless of the timeout state? It would certainly make life easier on me in PHP land if this was the case. -Rasmus