Morning,
hmm if I recall correctly the Apache guys removed PHP from their default
httpd.conf about 3 years ago, because they considered us a security threat.
And now the same people dare to demand more Apache 2 support from us?
Sorry Apache 2 folks. From my point of view, it is entirely your
problem, that people do not want your Apache 2 because they believe that
it cannot be used with PHP.
If you want better support then write it.
Just my 3 cents ;)
Stefan
"From my point of view, it is entirely your
problem, that people do not want your Apache 2 because they believe that
it cannot be used with PHP."
2nd that
Personally, I don't think this is a very constructive approach. I'm not
gonna promote the usage of Apache 2, but let's face it, Apache needs PHP and
PHP needs Apache. Let's not be arrogant and look at the issue at hand.
People don't use Apache 2 because of 2 reasons:
- There is not much reason to upgrade from Apache 1.3 to 2 in the first
place - It's discouraged by php.net and users of PHP
The question that people need to have answered is: Why, if this is the case,
is Apache 2 a bad choice for PHP? And if this problem is to be resolved,
where should this logically take place, Apache or PHP? Logically as in, what
would make sense from a rational and technical point of view, not from a
"it's your problem, you deal with it"-point of view.
Just my $0,02.
Ron Korving
"From my point of view, it is entirely your
problem, that people do not want your Apache 2 because they believe that
it cannot be used with PHP."2nd that