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
