William A. Rowe, Jr. wrote:
At 02:18 PM 11/10/2003, you wrote:
Bill Stoddard wrote:
[...]
Any ideas how to avoid the second call to initalize_module when I run as a service ?
You can't avoid the second call but there are ways to gracefully handle it. Here is a snip of code from a module I
Jeff Trawick wrote:
[...]
Since the work arounds (such as Bill suggested) are required for 1.3
and 2.0
compatiblity already, it seems we should focus on 2.1 and solve this
for good.
as far putting a solution in 2.0, what is it our concern if a module
wants to support only Apache = 2.0.50?
On Nov 13, 2003, at 2:43 PM, Jeff Trawick wrote:
ap_mpm_query(), implemented by each MPM, would need some help from
core to determine which pass of the pre/post-config hook it is, since
that is out of the MPM's domain.
It seems to me that the proposed patch (for modules) elegantly solves
a
Jim Jagielski wrote:
On Nov 13, 2003, at 2:43 PM, Jeff Trawick wrote:
ap_mpm_query(), implemented by each MPM, would need some help from
core to determine which pass of the pre/post-config hook it is, since
that is out of the MPM's domain.
It seems to me that the proposed patch (for modules)
Hello guys.
I'm running Apache2 on WindowsXP as a service(path to executable=
"c:\apache2\Apache.exe" -k runservicein my service configuration)
.
I have also ap_hook_post_config(initialize_module,NULL,NULL,APR_HOOK_MIDDLE)
in my source code...
The problem I have is that when
run
Bill Stoddard wrote:
[...]
Any ideas how to avoid the second call to initalize_module when I
run as a service ?
You can't avoid the second call but there are ways to gracefully handle
it. Here is a snip of code from a module I developed a while back:
[...]
and I posted a patch which
At 02:18 PM 11/10/2003, you wrote:
Bill Stoddard wrote:
[...]
Any ideas how to avoid the second call to initalize_module when I run as a
service ?
You can't avoid the second call but there are ways to gracefully handle it. Here is
a snip of code from a module I developed a while back:
William A. Rowe, Jr. wrote:
At 02:18 PM 11/10/2003, you wrote:
Bill Stoddard wrote:
[...]
Any ideas how to avoid the second call to initalize_module when I run as a service ?
You can't avoid the second call but there are ways to gracefully handle it. Here is a snip of code from a module I
