Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 54139 invoked by uid 500); 13 Oct 2001 01:46:57 -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 54118 invoked from network); 13 Oct 2001 01:46:57 -0000 Content-Type: text/plain; charset="iso-8859-1" From: Ryan Bloom Reply-To: rbb@covalent.net Organization: Covalent Technologies To: dev@httpd.apache.org, Dirk-Willem van Gulik Subject: Re: mod_asis; apr_bucket_file_create->destroy->poolcleanup->fileclose Date: Fri, 12 Oct 2001 18:46:46 -0700 X-Mailer: KMail [version 1.3] References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20011013014646.9EDA846DFC@koj.rkbloom.net> X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Friday 12 October 2001 05:23 pm, Dirk-Willem van Gulik wrote: > On Fri, 12 Oct 2001, Ryan Bloom wrote: > > The model is REALLY simple. apr_file_t's are created by apr_file_open, > > at that time, a cleanup is registered on the pool that was passed into > > the file_open function. apr_bucket_file_create just creates a bucket and > > puts the file into it. When the bucket is destroyed, the bucket is > > freed() and we check the refcount to determine if we should call > > apr_file_close. > > Hmm - I see it going to file_free(); but then not going to > apr_file_close(). but I get the gist now - digging deeper. According to Cliff's message, it won't, because that is done through the pool_cleanup that was registered when the file was opened. Ryan ______________________________________________________________ Ryan Bloom rbb@apache.org Covalent Technologies rbb@covalent.net --------------------------------------------------------------