Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (nike.apache.org: local policy)
From: Stefan Fritsch <sf@sfritsch.de>
To: dev@httpd.apache.org
Subject: Re: ap_read_config in 2.3.11
Date: Mon, 11 Apr 2011 21:14:53 +0200
User-Agent: KMail/1.13.5 (Linux/2.6.38-2-amd64; KDE/4.4.5; x86_64; ; )
References: <201104112045.55493.torsten.foertsch@gmx.net>
In-Reply-To: <201104112045.55493.torsten.foertsch@gmx.net>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Message-Id: <201104112114.53451.sf@sfritsch.de>

On Monday 11 April 2011, Torsten F=F6rtsch wrote:
> I am working on porting modperl to the upcoming httpd 2.4. One
> problem is the line
>=20
>   conf_vector_length =3D total_modules;
>=20
> in ap_read_config (config.c:2300).
>=20
> Modperl provides a way to write modules in Perl. These modules are
> loaded by the directive PerlLoadModule which is executed later
> than line 2300. Such modules are then appended to the module list,
> get a module structure, can create config directives etc. They
> also have a module index and allocate their place in config
> vectors.
>=20
> Now, the line above limits the config vector length to the number
> of modules known before any one perl module could be loaded.
>=20
> How can this situation be solved?

When exactly is PerlLoadModule executed? The above code assumes that=20
modules are loaded with EXEC_ON_READ during reading of the config.

I guess the optimization could be done later, after the config has=20
been parsed completely. That would waste some memory in pconf but=20
still preserve the optimization during request processing, which is=20
more important.