Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 86961 invoked by uid 500); 1 Jan 2002 02:15:19 -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 86950 invoked from network); 1 Jan 2002 02:15:18 -0000 Message-ID: <3C311BBF.1020406@cnet.com> Date: Mon, 31 Dec 2001 18:15:27 -0800 From: Brian Pane User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.5) Gecko/20011011 X-Accept-Language: en-us MIME-Version: 1.0 To: dev@httpd.apache.org Subject: filter registration question Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Is there any scenario in which a new filter can be registered at any time after server startup? There are a lot of places in the httpd where we add filters with hardcoded names, like ap_add_output_filter("SUBREQ_CORE", NULL, rnew, rnew->connection); I'd like to look up and cache the filter object for each of these names in a post-config function, to eliminate the name-to-filter mapping during request processing. But that won't work if it's possible for the filter registrations to subsequently change. --Brian