Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:47581
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.220 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        b=RquOKPq6NBMsJ1GZ/9PsLlqo/IKpj7Ofu3ph6DjPyuwRr/tPScD4FqCNa4dtOZ1Ta4
         xQOJzOwjk07s6fmJRPhWUbuvS3oz4JhQNA0mJq+73ukxMp1LdgwevRM8O3kGQE8W62jW
         1iYmNQmmcXZb4ptBauPwnjL30HlskoPBoVyH8=
MIME-Version: 1.0
In-Reply-To: <F8A64164-50D5-41BB-BF7B-6D96BF028C72@pooteeweet.org>
References: <3EC72D91-EA33-4175-B9F5-E1A61757916B@pooteeweet.org>
	 <7f3ed2c31003241310nad662e1uad7d5bbe8f985e5@mail.gmail.com>
	 <F8A64164-50D5-41BB-BF7B-6D96BF028C72@pooteeweet.org>
Date: Wed, 24 Mar 2010 21:26:17 +0100
Message-ID: <7f3ed2c31003241326s298cf2a4r19ec7746c4645cc8@mail.gmail.com>
To: Lukas Kahwe Smith <mls@pooteeweet.org>
Cc: PHP Developers Mailing List <internals@lists.php.net>, Michael Wallner <mike@php.net>, Jani Taskinen <jani@php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] Output buffering patch
From: hannes.magnusson@gmail.com (Hannes Magnusson)

On Wed, Mar 24, 2010 at 21:12, Lukas Kahwe Smith <mls@pooteeweet.org> wrote:
>
> On 24.03.2010, at 21:10, Hannes Magnusson wrote:
>
>> On Wed, Mar 24, 2010 at 11:54, Lukas Kahwe Smith <mls@pooteeweet.org> wrote:
>>> Hey,
>>>
>>> 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.
>>>
>>
>> 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.
>>
>> Is there really anyone who doesn't want this committed? For what reason?
>
>
> 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.
>

Search the archives. Do your homework.

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.

You cannot seriously be expecting more then that, nearly 4years later?

Some links to get you started:
http://php.markmail.org/message/ujx2htvdzerrxgfe?q=README.NEW-OUTPUT-API+from:%22Michael+Wallner%22+order:date-forward
http://php.markmail.org/message/n22c6ye5boe2rtjk?q=README.NEW-OUTPUT-API+from:%22Michael+Wallner%22+order:date-forward&page=1
http://php.markmail.org/message/jgsd2umnm5lk37b6?q=README.NEW-OUTPUT-API+from:%22Michael+Wallner%22+order:date-forward&page=1

-Hannes