Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:45539
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain seanius.net from 66.93.22.232 cause and error)
Date: Wed, 9 Sep 2009 10:56:48 +0200
To: Jani Taskinen <jani.taskinen@iki.fi>
Cc: dreamcat four <dreamcat4@gmail.com>, internals@lists.php.net
Message-ID: <20090909085648.GA14146@rangda.stickybit.se>
References: <99cf22520909081652v29a9ea56q33882849cce3081e@mail.gmail.com>
 <4AA6F06C.4020008@lerdorf.com>
 <99cf22520909081814w64ef896rbf1bffda9354e72c@mail.gmail.com>
 <4AA70384.7020705@zend.com>
 <99cf22520909081942yd7b0b68m4354c918687b8633@mail.gmail.com>
 <20090909055541.GA9004@rangda.stickybit.se>
 <4AA75D6D.9000802@iki.fi>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="BOKacYhQ+x31HxR3"
Content-Disposition: inline
In-Reply-To: <4AA75D6D.9000802@iki.fi>
User-Agent: Mutt/1.5.20 (2009-06-14)
Subject: Re: [PHP-DEV] [sapi] PHP-FPM (FastCGI Process Manager), by Andrei
 Nigmatulin - upstream Y/n?
From: seanius@seanius.net (sean finney)

--BOKacYhQ+x31HxR3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Sep 09, 2009 at 10:46:53AM +0300, Jani Taskinen wrote:
> Yeah, NO THANKS. We have enough of unmaintained code already. Since
> you want this fpm thing into upstream PHP releases, why not make the
> changes into libevent go upstream as well and then reconsider
> bundling, merging, etc.

that seems a natural corollary, yes.  that or remove the need for making
the local modifications in the first place.  i'm not at all familiar
with the fpm project so wasn't aware of this until it was brought up, and
i don't know the specifics of how/why the library has been modified.

i should also point out that it's not exactly that *I* want this to be
included in php... all i know is that as a general rule when someone
comes along saying "hey can you apply this huge patch for a new feature",
i'm inclined to first point them at the upstream developers to try to
get it sorted out there. =20

this allows for a certain level of code review and the chance to get an
idea of what you think of the feature, as well as potentially benefitting
the entire php user base (if you take it) vs. the limited one of those
using debian-derived php packages (if we take it).  and if you don't
like/want the patch, it would be good to know the reasons as it'd help
us decide whether or not we want it too.


	sean

--=20

--BOKacYhQ+x31HxR3
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iD8DBQFKp23QynjLPm522B0RAvbjAKCFLeFxrEAOMUCwN1hMKfM9huIfVgCfdgPA
PJ1ltRI6wZTr+jJ/15Kl9c0=
=GjC4
-----END PGP SIGNATURE-----

--BOKacYhQ+x31HxR3--