Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 84057 invoked by uid 500); 5 Jun 2001 20:58:55 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 84044 invoked from network); 5 Jun 2001 20:58:55 -0000 Date: Tue, 5 Jun 2001 14:01:01 -0700 (PDT) From: X-Sender: To: "'new-httpd@apache.org'" Subject: RE: file/mmap buckets, subrequests, pools, 2.0.18 In-Reply-To: <3482305AF0F6CF469ED45C0D48FAFCF7091FF462@cnet48.cnet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N > > On Mon, Jun 04, 2001 at 10:13:30AM -0700, Ian Holsman wrote: > > > couldn't we have it so that the 'sub-handlers' request pool > > is joined with/the same as the main request's pool, > > > (this is different to the 'connection' pool right?) > > > > > > so that sub-requests live for the life of the request... > > > It looks like that is what the function apr_pool_join does > > in 'debug' mode > > > > No... The whole point of having a subrequest pool is so that > > we can trash it > > when the subrequest is done. If a request ran 1000 subrequests (it can > > happen with a large directory processed by mod_autoindex), > > then you would > > end up with a HUGE waste of memory in the request pool. > > > > > Passing a pool to setaside() should allow us to migrate a > > bucket from one > > pool/lifetime (the subrequest) to another pool/lifetime (the > > request or the > > connection depending on who does a setaside and where they > > want to put it). > > > > ok thats sounds fair.. > > the only problem i can see is that most bucket types don't implement the setaside function > is implementing the setaside (with a pool) going to fix the mod_include problem of not > having the buckets passed back? Greg's idea requires that more buckets implement the setaside function. The other idea of just having the sub_request_filter handle the problem doesn't have that requirement. Ryan _______________________________________________________________________________ Ryan Bloom rbb@apache.org 406 29th St. San Francisco, CA 94131 -------------------------------------------------------------------------------