Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:30155
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
To: internals@lists.php.net,Brian Moon <brianm@dealnews.com>
Message-ID: <46701499.2010803@ntlworld.com>
Date: Wed, 13 Jun 2007 17:00:25 +0100
User-Agent: Thunderbird 2.0.0.0 (Windows/20070326)
MIME-Version: 1.0
References: <46700D62.4050901@dealnews.com>
In-Reply-To: <46700D62.4050901@dealnews.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: apache_child_terminate on Apache 2.x
From: scottmacvicar@ntlworld.com (Scott MacVicar)

It's simply not supported within the Apache API any more, they removed
it between 1.3 and 2.0 due to the new MPM structure where a child
process was no longer serving only one request but could be serving dozens.

With the Worker MPM by default each child serves 25 requests, so it
wasn't practical to mark something to exit at the end of a request.

Scott

Brian Moon wrote:
> So, Gentoo has removed Apache 1.3 from Portage.  RedHat and others has
> not installed it for years.  Frankly, the only reason we have for
> sticking with 1.3 is the lack of apache_child_terminate support in PHP
> for Apache 2.
> 
> Does Apache 2 simply not provide this anymore?  Was it left out for a
> philosophical reason?  Was it just over looked?  Like it or not, PHP is
> gonna have to work well on Apache 2 at some point.  I don't like it, but
> its reality.  AFAIK, this is the only apache function that does not work
> in Apache 2.
>