Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:53710
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain no-surprises.co.uk designates 80.68.93.37 as permitted sender)
Message-ID: <4E0CEBDC.6050206@no-surprises.co.uk>
Date: Thu, 30 Jun 2011 22:34:20 +0100
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110516 Thunderbird/3.1.10
MIME-Version: 1.0
To: Stas Malyshev <smalyshev@sugarcrm.com>
CC: PHP internals <internals@lists.php.net>
References: <4E0CE015.80503@no-surprises.co.uk> <4E0CEAC5.3070800@sugarcrm.com>
In-Reply-To: <4E0CEAC5.3070800@sugarcrm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Improvements to HTTP stream metadata
From: michael@no-surprises.co.uk (Michael Maclean)

On 30/06/11 22:29, Stas Malyshev wrote:
> Hi!
>
> On 6/30/11 1:44 PM, Michael Maclean wrote:
>> * move the current contents of the wrapper_data array to a key called
>> 'headers' within wrapper_data;
>
> This means breaking every script in existence that uses this data now.
> Probably not a good idea. Maybe we should think about a BC way to do the
> same.

Yeah; I'm open to suggestions on that front. I couldn't really think of 
another way to do it.

The same data also ends up in the bizarre $http_response_headers var 
that gets spontaneously created in local scope - I've wondered about how 
good that is to do.

-- 
Cheers,
Michael