Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:47583
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 188.40.37.16 cause and error)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <7f3ed2c31003241326s298cf2a4r19ec7746c4645cc8@mail.gmail.com>
Date: Wed, 24 Mar 2010 21:41:16 +0100
Cc: PHP Developers Mailing List <internals@lists.php.net>,
 Michael Wallner <mike@php.net>,
 Jani Taskinen <jani@php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <6478E1F4-8DFD-4D7E-A83C-8014A1411D26@pooteeweet.org>
References: <3EC72D91-EA33-4175-B9F5-E1A61757916B@pooteeweet.org> <7f3ed2c31003241310nad662e1uad7d5bbe8f985e5@mail.gmail.com> <F8A64164-50D5-41BB-BF7B-6D96BF028C72@pooteeweet.org> <7f3ed2c31003241326s298cf2a4r19ec7746c4645cc8@mail.gmail.com>
To: Hannes Magnusson <hannes.magnusson@gmail.com>
Subject: Re: [PHP-DEV] Output buffering patch
From: mls@pooteeweet.org (Lukas Kahwe Smith)


On 24.03.2010, at 21:26, Hannes Magnusson wrote:

> On Wed, Mar 24, 2010 at 21:12, Lukas Kahwe Smith <mls@pooteeweet.org> =
wrote:
>>=20
>> On 24.03.2010, at 21:10, Hannes Magnusson wrote:
>>=20
>>> On Wed, Mar 24, 2010 at 11:54, Lukas Kahwe Smith =
<mls@pooteeweet.org> wrote:
>>>> Hey,
>>>>=20
>>>> Could one of you write up a short RFC on this patch? Just some =
details about the bugs fixed, known BC breaks and (undocumented) edge =
case changes. This would be helpful for anyone wanting to review their =
code and testing as well as documentation.
>>>>=20
>>>=20
>>> I really do not see why this even needs a discussion. Its been in
>>> trunk for years already. People have had plenty of time to give
>>> feedback.
>>>=20
>>> Is there really anyone who doesn't want this committed? For what =
reason?
>>=20
>>=20
>> This isnt about getting a reason not to commit this. As you can see =
in the above quoted mail from me, I was asking for this RFC for various =
other reasons.
>>=20
>=20
> Search the archives. Do your homework.
>=20
> 3 years and 9 months ago the patch was posted to internals for review.
> It included README files, TODO list, tests, tests, tests and =
explanations.
> Few weeks later it got committed.
> The commit got reviewed by various parties and some enhancements were =
made.
> Every single procedure was followed to the letter.
> People were happy.
>=20
> You cannot seriously be expecting more then that, nearly 4years later?

All I am asking is a single document in the central location we have =
dedicated for this (aka the rfc namespace on the wiki), that pulls =
together all relevant documentation. If all that is needed is a copy =
paste of a bunch of URL's all the better. But it makes no sense to ask =
each and every developer to "do his homework". Thats a waste of time and =
a sure way to have misunderstandings.

Seems like you know all there is to know about this, so how about just =
throwing together an RFC, shouldnt take more than 10 minutes if all of =
this is already perfectly documented.

> Some links to get you started:
> =
http://php.markmail.org/message/ujx2htvdzerrxgfe?q=3DREADME.NEW-OUTPUT-API=
+from:%22Michael+Wallner%22+order:date-forward
> =
http://php.markmail.org/message/n22c6ye5boe2rtjk?q=3DREADME.NEW-OUTPUT-API=
+from:%22Michael+Wallner%22+order:date-forward&page=3D1
> =
http://php.markmail.org/message/jgsd2umnm5lk37b6?q=3DREADME.NEW-OUTPUT-API=
+from:%22Michael+Wallner%22+order:date-forward&page=3D1


These links just highlight that there are questions, not that there are =
answers.

regards,
Lukas Kahwe Smith
mls@pooteeweet.org