William A. Rowe, Jr. wrote:
One of three things can happen here... please express your preference
(if you have one)
[ ] Change the MPM code to use Apache2.2 by default (and Apache2.4 in trunk)
[X] Change the Installer to go back to Apache2 as the default service
(this makes
William A. Rowe, Jr. wrote:
The default service name is Apache2, both in the 2.0 and 2.2 WinNT MPMs.
One of three things can happen here... please express your preference
(if you have one)
[ ] Change the MPM code to use Apache2.2 by default (and Apache2.4 in trunk)
[X] Change the Installer
hello,
I am trying to implement a new layer for Apache http server. It means i
will insert a new layer between tcp and http protocol and accordingly the
Apache will listen to the connection from this layer instead of tcp layer,
creating the socket. This funcitonality works correctly if i set
On Wed, Jan 03, 2007 at 04:54:59PM -0500, Tim Olsen wrote:
Hello,
I'm not very familiar with autoconf so forgive me if I'm wrong, but it
looks like AC_MSG_NOTICE is not in autoconf 2.13 but it is being used
by buildconf which specifies an AC_PREREQ(2.13)
Thanks for the report - I've fixed
William A. Rowe, Jr. wrote:
The default service name is Apache2, both in the 2.0 and 2.2 WinNT MPMs.
With the installer, I had tweaked (a separate setting) the service name
default to be Apache2.2. HOWEVER, when users transition from the .msi
installed version to the command line, they are
On Jan 3, 2007, at 10:49 PM, William A. Rowe, Jr. wrote:
[ ] Change the MPM code to use Apache2.2 by default (and Apache2.4
in trunk)
[X] Change the Installer to go back to Apache2 as the default service
(this makes parallel installs of Apache2.0 and Apache2.2 more
troublesome.)
[
Sander Temme wrote:
On Jan 3, 2007, at 10:49 PM, William A. Rowe, Jr. wrote:
[X] Change the Installer to go back to Apache2 as the default service
(this makes parallel installs of Apache2.0 and Apache2.2 more
troublesome.)
Changing the service name would violate the Principle of
