Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 69807 invoked by uid 500); 18 Sep 2001 10:49:35 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 69784 invoked from network); 18 Sep 2001 10:49:35 -0000 X-Authentication-Warning: rdu88-250-106.nc.rr.com: trawick set sender to trawick@attglobal.net using -f Sender: trawick@rdu88-250-106.nc.rr.com To: dev@httpd.apache.org Subject: Re: New post-log-transaction hook? References: <20010917155221.A15053@covalent.net> <20010918021042.M1627@lyra.org> From: Jeff Trawick Date: 18 Sep 2001 06:52:35 -0400 In-Reply-To: <20010918021042.M1627@lyra.org> Message-ID: Lines: 20 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Greg Stein writes: > 2) move the ap_lingering_close inside ap_process_connection, then call it > from with ap_process_connection. This *almost* works. All MPMs have a > call to ap_process_connection followed by a call to ap_lingering_close. > The only MPM that does other funny stuff in there is the winnt MPM. > Conceivably, you could pass a flag that says "I'll manage the shutdown, > thankyouvermuch", and winnt would do its close followed by the > post-connection hook. It is nice for ap_lingering_close() to be handled in the MPM. It shouldn't be too hard for the MPM to implement its own lingering close in a manner that doesn't consume one thread per closing connection (e.g., dedicate one thread per MPM to do all the lingering close logic). Of course there could always be another hook :) -- Jeff Trawick | trawick@attglobal.net | PGP public key at web site: http://www.geocities.com/SiliconValley/Park/9289/ Born in Roswell... married an alien...