Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:14157 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 76281 invoked by uid 1010); 22 Dec 2004 15:50:15 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 73041 invoked by uid 1007); 22 Dec 2004 15:49:51 -0000 Message-ID: <20041222154951.72966.qmail@pb1.pair.com> To: internals@lists.php.net References: <41C7E535.6060908@php.net> Date: Wed, 22 Dec 2004 16:46:29 +0100 Lines: 28 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Posted-By: 62.58.68.2 Subject: Re: [PHP-DEV] About Apache 2 demands From: r.korving@xit.nl ("Ron Korving") 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: 1) There is not much reason to upgrade from Apache 1.3 to 2 in the first place 2) 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