Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:3846
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <20030809230710.48445.qmail@pb1.pair.com>
To: internals@lists.php.net
References: <20030809210710.97648.qmail@pb1.pair.com> <200308091839.42975.ilia@prohost.org>
Date: Sat, 9 Aug 2003 20:07:06 -0300
Lines: 64
Subject: Re: [PHP-DEV] Apache2
From: cunha17@uol.com.br ("Cristiano Duarte")

Despite all warning and the EXPERIMENTAL label, I'm using Apache2 on
production since last year.
IMHO, the new features available (filter modules) and the complete rewrite
of some parts made Apache2 very attractive and faster (YMMV).
I implemented UFU (User Friendly URLs) in apache (httpd.conf) using some
modules and it works great !
After this, some improvements on the server(optimization, PHPA cache) and
the new MVC framework I designed, my Java developer stopped making fun of
PHP. And when I told him about the new features of PHP5 he realized that his
effords to make Java the default development language in my company (instead
of PHP) would lead to /dev/null.
It were not a "bed of roses", I still have some problems specially with the
size of apache process using PHP (10-20 Mb each). So I limited the number of
concurrent apache process and now it works smoothly on a P4 with 512Mb RAM.

Cristiano Duarte


"Ilia Alshanetsky" <ilia@prohost.org> escreveu na mensagem
news:200308091839.42975.ilia@prohost.org...
> I wouldn't worry about the EXPERIMENTAL label, but rather whether the
PHP's
> Apache 2 interface works for you and if there are any bug reports that may
> affect you. Personally, I do not yet see a reason to switch to Apache 2
from
> Apache 1, but that's just me. Comparatively speaking, Apache 1 PHP
interface
> has been used & developed for several years, while Apache 2 interface
> (current implementation) is less then a year old. Every release we fix
> several bugs, which at least in part responsible for it's EXPERIMENTAL
> status.
>
> >Is this the responsibility of the PHP QA team?
>
> QA team is a very small group of people who work very hard at solving
bugs,
> but time constraits and the scale task do not allow us to cover
everything.
> Priority is given to commonly used extensions and configuration. As far as
I
> am concerned Apache 2 is not as high on the priority list as Apache 1 or
> MySQL, etc...
>
> > Can users help out with testing?
>
> Definitely, try PHP releases as they come out, especially the Release
> Candidates (RC) and report any bugs that you find. If you can suggest a
patch
> to the problem, even better :).
>
> > Redhat apparently feels
> > confident enough to include Apache 2 (and PHP4) in their upcoming Redhat
> > Enterprise 3 product
> >
(http://ftp.redhat.com/pub/redhat/linux/beta/taroon/en/as/i386/RELEASE-NOTE
> >S -en), so I assume that at least they have tested it.
>
> Redhat released a beta compiler despite warnings from developers of said
> compiler.
>
> Ilia
>