Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 97209 invoked by uid 500); 22 Apr 2000 01:02:59 -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 97196 invoked from network); 22 Apr 2000 01:02:59 -0000 Date: Fri, 21 Apr 2000 18:09:39 -0700 (PDT) From: Greg Stein To: grisha@verio.net, new-httpd@apache.org Subject: Re: destroy_dir_config ? In-Reply-To: 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 On Fri, 21 Apr 2000 grisha@verio.net wrote: > Sorry if this is a dumb question or if I'm posting to the wrong list! This is close. The apache-modules list is probably a bit closer. See http://modules.apache.org/subscribe#API > Am I right to conclude that there is no destroy_dir_config (or anything > that provides such functionality), Correct. But... > so any memory in create_dir_config > handle MUST be allocated using apache routines that use pools, or you > never get a chance to free that memory? > > I'm writing a module where I would prefer to store the config values in a > Python structure (this is for mod_python), but Python cannot use Apache > pools - am I SOL? > > Is there any kind of an event that I can hook so that when a pool is > destroyed, I can do some of my own destruction? Yes. Take a look at the ap_register_cleanup() function and its friends. This will give you a chance to call Py_DECREF() when the pool goes away. Cheers, -g -- Greg Stein, http://www.lyra.org/