Hi all,
On Wed, Feb 4, 2015 at 3:42 PM, Stanislav Malyshev
wrote:
> > About $php_errormsg , we have error_get_last().
> > About $http_response_headers, we have no replacement.
> >
> > Why not get rid of both ?
>
> I agree. Magically appearing variables are bad design and if we can get
> rid of t
On Fri, Mar 27, 2015 at 7:12 PM, Rowan Collins
wrote:
> Ferenc Kovacs wrote on 27/03/2015 16:50:
>
>> yeah, but we already mentioned/discussed this that the removal would
>> require introducing another way (eg. adding a method) for fetching the
>> headers.
>> I think that introducing this method
Ferenc Kovacs wrote on 27/03/2015 16:50:
yeah, but we already mentioned/discussed this that the removal would
require introducing another way (eg. adding a method) for fetching the
headers.
I think that introducing this method can happen in a minor version(without
removing the $http_response_head
On Fri, Mar 27, 2015 at 5:42 PM, Ralph Schindler
wrote:
>
> About $php_errormsg , we have error_get_last().
About $http_response_headers, we have no replacement.
Why not get rid of both ?
>>>
>>> I agree. Magically appearing variables are bad design and if we can get
>>> rid
About $php_errormsg , we have error_get_last().
About $http_response_headers, we have no replacement.
Why not get rid of both ?
I agree. Magically appearing variables are bad design and if we can get
rid of them, PHP 7 is the time.
--
Stas Malyshev
smalys...@gmail.com
did we miss the oppo
On Wed, Feb 4, 2015 at 7:42 AM, Stanislav Malyshev
wrote:
> Hi!
>
> > About $php_errormsg , we have error_get_last().
> > About $http_response_headers, we have no replacement.
> >
> > Why not get rid of both ?
>
> I agree. Magically appearing variables are bad design and if we can get
> rid of th
Hi!
> About $php_errormsg , we have error_get_last().
> About $http_response_headers, we have no replacement.
>
> Why not get rid of both ?
I agree. Magically appearing variables are bad design and if we can get
rid of them, PHP 7 is the time.
--
Stas Malyshev
smalys...@gmail.com
--
PHP Inte
> On 03 02 2015, at 10:33, Julien Pauli wrote:
>
> $HTTP_RAW_POST_DATA could as well disappear (made deprecated as of 5.6).
>
This is already gone in master, which reminds me of the missing UPGRADING note.
Regards,
Mike
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe
On 2/3/15 3:33 AM, Julien Pauli wrote:
On Mon, Feb 2, 2015 at 6:19 PM, Ferenc Kovacs wrote:
About $php_errormsg , we have error_get_last().
About $http_response_headers, we have no replacement.
Well, we sort of do. You can get header information from the http
context stream metadata:
On Tue, Feb 3, 2015 at 10:33 AM, Julien Pauli wrote:
> On Mon, Feb 2, 2015 at 6:19 PM, Ferenc Kovacs wrote:
>
>> On Tue, Dec 2, 2014 at 11:28 AM, Ferenc Kovacs wrote:
>>
>> >
>> >
>> > On Tue, Dec 2, 2014 at 1:08 AM, Rowan Collins
>> > wrote:
>> >
>> >> On 1 December 2014 22:28:04 GMT, Ralph S
On Mon, Feb 2, 2015 at 6:19 PM, Ferenc Kovacs wrote:
> On Tue, Dec 2, 2014 at 11:28 AM, Ferenc Kovacs wrote:
>
> >
> >
> > On Tue, Dec 2, 2014 at 1:08 AM, Rowan Collins
> > wrote:
> >
> >> On 1 December 2014 22:28:04 GMT, Ralph Schindler <
> >> ra...@ralphschindler.com> wrote:
> >> >Hi all,
> >
On Tue, Dec 2, 2014 at 11:28 AM, Ferenc Kovacs wrote:
>
>
> On Tue, Dec 2, 2014 at 1:08 AM, Rowan Collins
> wrote:
>
>> On 1 December 2014 22:28:04 GMT, Ralph Schindler <
>> ra...@ralphschindler.com> wrote:
>> >Hi all,
>> >
>> >Many of you know from reading the subject line whats coming next! ;)
Tom Samplonius wrote on 02/12/2014 05:01:
Wow, I had no idea that existed; what an incredibly ugly
implementation. Even the name is weird (why "header" singular when it
contains an array of headers?)
Actually, no. HTTP responses contain a single header at the
protocol level, but contain
On Tue, Dec 2, 2014 at 1:08 AM, Rowan Collins
wrote:
> On 1 December 2014 22:28:04 GMT, Ralph Schindler
> wrote:
> >Hi all,
> >
> >Many of you know from reading the subject line whats coming next! ;)
> >
> >In php, after we interact with HTTP streams (as a client), PHP conjures
> >
> >into local
> I think that usage may have originated in PHP, actually.
Eh, dunno about that...
http://lists.w3.org/Archives/Public/ietf-http-wg-old/1995SepDec/0277.html
for example.
Even some W3C specs use "header" instead of the more accurate "header
field" so it's kind of a done deal.
-- S.
--
PHP Inter
>
> Wow, I had no idea that existed; what an incredibly ugly implementation. Even
> the name is weird (why "header" singular when it contains an array of
> headers?)
Actually, no. HTTP responses contain a single header at the protocol level,
but contain multiple lines. At some point, peopl
On 1 December 2014 22:28:04 GMT, Ralph Schindler
wrote:
>Hi all,
>
>Many of you know from reading the subject line whats coming next! ;)
>
>In php, after we interact with HTTP streams (as a client), PHP conjures
>
>into local scope a variable with header information from the previous
>request $h
17 matches
Mail list logo
