Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:14222
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <41D19DE9.4090600@php.net>
Date: Tue, 28 Dec 2004 12:54:49 -0500
User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206)
MIME-Version: 1.0
To: Hans Zaunere <hans@nyphp.com>
CC: Lester Caine <lester@lsces.co.uk>, internals@lists.php.net
References: <41EE526EC2D3C74286415780D3BA9F87073481D1@ehost011-1.exch011.intermedia.net>
In-Reply-To: <41EE526EC2D3C74286415780D3BA9F87073481D1@ehost011-1.exch011.intermedia.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Why we don't like PHP /
From: rasmus@php.net (Rasmus Lerdorf)

Hans Zaunere wrote:
> That presents somewhat of a chicken-and-egg problem.  Production sites
> won't be compelled to make a move until PHP recommends it in some way,
> or if there is a killer feature that pulls people in, regardless of the
> perceived stability.

Right, and they shouldn't.  If there is no compelling reason to switch, 
why in the world should they?  And why should we try to push them away 
from a stable platform?

> Then perhaps some striking new functionality would push PHP 5/Apache 2.
> While Apache 2 introduces new complexities, using some of the new
> features could be advantageous, and a step towards the next generation.
> For instance, allowing PHP to reach deeper into Apache, to a level
> similar to that of mod_perl, could provide significant new features and
> value.  Getting PHP to control URL rewriting and logging, for example,
> could be new features that drive demands from end-developers, and at the
> same time generates interest and challenges for those developing PHP and
> Apache themselves.

That has nothing to do with Apache2 and has been available for Apache1 
for years.  It just isn't a very popular feature.  See the apache_hooks 
code.

-Rasmus