Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:17760
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
	s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=cz9rFwNHNbamjlag3rMcPxd9iYKuVmY7WXe7qPjVonjoTmdIq9SaRixA0DeYCWFv7DVB/0wu0hNvgbGF5+XxrOv+2ZRQJwOt/VQXh9NXh4oOEKjbGleEYEivIiQpJqAMEsMqI55uLUQdq1S6HuxVzTXgEpOUEKQf1VU7QE5naWg=
Message-ID: <57792e8505080917402f144072@mail.gmail.com>
Date: Tue, 9 Aug 2005 17:40:10 -0700
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Cc: internals@lists.php.net
In-Reply-To: <42F9217F.6010604@lerdorf.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <57792e85050808205143e96a8f@mail.gmail.com>
	<42F907A0.8070900@web.de> <57792e85050809142416ee5d6c@mail.gmail.com>
	<42F9217F.6010604@lerdorf.com>
Subject: Re: [PHP-DEV] Re: Moving to PHP5.1 and Apache 2.2 next year, need help
From: iamstever@gmail.com (steve roussey)

On 8/9/05, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:
> PHP by default compiles as a non-pic shared library now which is just as
> fast as a static build inside Apache since it is the pic stuff that
> slows down a DSO.  So there is really no need for static builds anymore,
> unless you happen to be on a fringe OS that doesn't support non-pic
> shared libs.

This is good to know. I guess it is time to rewrite my
build-a-new-webserver script. It has seen changes over the years but
not a comprehensive reevaluation.

> > Still, I looked at lighttpd and it looks promising. The one thing that
> > started all of this was Apache 2.1's event MPM that used a single
> > thread to handle all open Keep-Alives looked very efficient.
>=20
> I think you are probably better off solving this in a lightweight
> frontend process.  Chances are you are going to need lingerd if you go
> keepalive, so perhaps the real solution is to make lingerd handle not
> just the shutdown, but also the startup of the request.

You know, I remember considering lingerd a long time ago... and I feel
like an idiot for not using all these years! If it is not in my script
it doesn't cross my mind. So I have that on today's todo list. (This
seems like something Apache2 should do automatically in its threaded
MPMs, not that we would be using mod_php here or anything, but maybe

I am confused by your statement above, so I have tried not to email
back until I could find more information, but I could not. In the
lingerd website it says "lingerd can only do an effective job if HTTP
Keep-Alives are turned off" which is confusing when compared to your
statement above. Unless you are combining it with the lightweight
process (I assume a proxy server). Then it makes sense. Except for the
part about having lingerd hande the startup of the request, at which
point I'm clueless again.