Re: [PHP-DEV] New Standardized HTTP Interface

On 10/31/14, 4:19 PM, Sherif Ramadan wrote: On Fri, Oct 31, 2014 at 5:01 PM, Will Fitch wrote: I’m actually not suggesting an alternative - I’m suggesting this RFC isn’t an option. Great, your suggestion has been noted. Thanks for your contribution to this discussion! :) Let's try a

Re: [PHP-DEV] New Standardized HTTP Interface

On Fri, Oct 31, 2014 at 5:01 PM, Will Fitch wrote: > > > > I’m actually not suggesting an alternative - I’m suggesting this RFC isn’t > an option. > > Great, your suggestion has been noted. Thanks for your contribution to this discussion! :)

Re: [PHP-DEV] New Standardized HTTP Interface

> On Oct 31, 2014, at 4:51 PM, Sherif Ramadan wrote: > > On Fri, Oct 31, 2014 at 4:29 PM, Will Fitch wrote: > >> >> On Oct 31, 2014, at 4:21 PM, Sherif Ramadan >> wrote: >> >> >> >> On Fri, Oct 31, 2014 at 4:16 PM, Will Fitch wrote: >> >>> >>> >>> >>> While not too specific to Rowan,

Re: [PHP-DEV] New Standardized HTTP Interface

On Fri, Oct 31, 2014 at 4:29 PM, Will Fitch wrote: > > On Oct 31, 2014, at 4:21 PM, Sherif Ramadan > wrote: > > > > On Fri, Oct 31, 2014 at 4:16 PM, Will Fitch wrote: > >> >> >> >> While not too specific to Rowan, reiterating the pecl/http approach is >> indirectly what your asking for? I have

[PHP-DEV] pecl/http RFC

I don’t want to restart any previous threads, but I’d like to get/restart the conversation going with the pecl/http RFC: https://wiki.php.net/rfc/pecl_http . Recent conversations regarding https://wiki.php.net/rfc/http-interface

Re: [PHP-DEV] New Standardized HTTP Interface

> On Oct 31, 2014, at 4:21 PM, Sherif Ramadan wrote: > > > > On Fri, Oct 31, 2014 at 4:16 PM, Will Fitch > wrote: > > > > While not too specific to Rowan, reiterating the pecl/http approach is > indirectly what your asking for? I have mentioned this numerous time

Re: [PHP-DEV] New Standardized HTTP Interface

On Fri, Oct 31, 2014 at 4:16 PM, Will Fitch wrote: > > > > While not too specific to Rowan, reiterating the pecl/http approach is > indirectly what your asking for? I have mentioned this numerous times, but > you haven’t responded with a reason not to take this approach - which is an > RFC that w

Re: [PHP-DEV] New Standardized HTTP Interface

> On Oct 31, 2014, at 4:05 PM, Sherif Ramadan wrote: > > On Fri, Oct 31, 2014 at 3:35 PM, Rowan Collins > wrote: > >> Sherif Ramadan wrote on 31/10/2014 18:52: >> >>> This RFC is about core PHP and I really don't care how >>> many competing ideas exist out there that are closely or mildly rel

Re: [PHP-DEV] New Standardized HTTP Interface

On Fri, Oct 31, 2014 at 3:35 PM, Rowan Collins wrote: > Sherif Ramadan wrote on 31/10/2014 18:52: > >> This RFC is about core PHP and I really don't care how >> many competing ideas exist out there that are closely or mildly related to >> this RFC. >> > > The decision about *whether this is neede

Re: [PHP-DEV] New Standardized HTTP Interface

Sherif Ramadan wrote on 31/10/2014 17:27: On Fri, Oct 31, 2014 at 1:09 PM, Rowan Collins mailto:rowan.coll...@gmail.com>> wrote: Let me repeat my question: Say I write a class "AwesomeHTTPReceive implements HttpMessageReceive", what do I then do with this class in order for

Re: [PHP-DEV] New Standardized HTTP Interface

Sherif Ramadan wrote on 31/10/2014 18:52: This RFC is about core PHP and I really don't care how many competing ideas exist out there that are closely or mildly related to this RFC. The decision about *whether this is needed in core* is not something you can ignore by saying "this is about cor

Re: [PHP-DEV] New Standardized HTTP Interface

On Fri, Oct 31, 2014 at 3:00 PM, Larry Garfield wrote: > On 10/31/14, 1:52 PM, Sherif Ramadan wrote: > >> >> > This RFC has two primary goals in mind: >> >> 1) Expose the parsing/handling of the HTTP request to userland in a >> consistent way >> > > It already is. It's the access TO that parsed

Re: [PHP-DEV] New Standardized HTTP Interface

On 10/31/14, 1:52 PM, Sherif Ramadan wrote: So for the purposes of this discussion and in an effort to remain on-topic and productive, let's keep all of the FIG/PSR and other third party efforts out of the discussion unless it is intended to improve/help this particular RFC. Please keep in mind t

Re: [PHP-DEV] New Standardized HTTP Interface

So for the purposes of this discussion and in an effort to remain on-topic and productive, let's keep all of the FIG/PSR and other third party efforts out of the discussion unless it is intended to improve/help this particular RFC. Please keep in mind that this is a PHP internals discussion and not

Re: [PHP-DEV] New Standardized HTTP Interface

On 10/31/14, 12:38 PM, Sherif Ramadan wrote: On Fri, Oct 31, 2014 at 1:32 PM, Florian Margaine wrote: Hi, Le 31 oct. 2014 18:28, "Sherif Ramadan" a écrit : On Fri, Oct 31, 2014 at 1:09 PM, Rowan Collins wrote: Let me repeat my question: Say I write a class "AwesomeHTTPReceive implemen

Re: [PHP-DEV] New Standardized HTTP Interface

On Fri, Oct 31, 2014 at 1:32 PM, Florian Margaine wrote: > Hi, > > Le 31 oct. 2014 18:28, "Sherif Ramadan" a écrit > : > > > > On Fri, Oct 31, 2014 at 1:09 PM, Rowan Collins > > wrote: > > > > > > > > Let me repeat my question: > > > > > > Say I write a class "AwesomeHTTPReceive implements Http

Re: [PHP-DEV] New Standardized HTTP Interface

Hi, Le 31 oct. 2014 18:28, "Sherif Ramadan" a écrit : > > On Fri, Oct 31, 2014 at 1:09 PM, Rowan Collins > wrote: > > > > > Let me repeat my question: > > > > Say I write a class "AwesomeHTTPReceive implements HttpMessageReceive", > > what do I then do with this class in order for it to perform

Re: [PHP-DEV] New Standardized HTTP Interface

On Fri, Oct 31, 2014 at 1:09 PM, Rowan Collins wrote: > > Let me repeat my question: > > Say I write a class "AwesomeHTTPReceive implements HttpMessageReceive", > what do I then do with this class in order for it to perform any actions? > > How does PHP know that my class is the one it should pop

Re: [PHP-DEV] New Standardized HTTP Interface

On Fri, Oct 31, 2014 at 12:04 PM, Andrea Faulds wrote: > > > > So there’s still a default implementation, then? So, if you want to parse > in userland, how does that work? The default implementation fills in the > variables and then your implementation parses it again, wasting CPU time > and maki

Re: [PHP-DEV] New Standardized HTTP Interface

On Fri, Oct 31, 2014 at 12:19 PM, Andrea Faulds wrote: > > > > I’m not sure I really see what it solves, though? Why should we allow > users to implement their own slow parsers in userland? Why can’t we just > have a single built-in parser like we’ve had the last two decades? I don’t > see the po

Re: [PHP-DEV] [RFC] GitHub Pull Requests Triage Team

> On Oct 31, 2014, at 12:10 PM, Andrea Faulds wrote: > > >> On 30 Oct 2014, at 21:57, John Bafford wrote: >> I would like to propose the creation of a team to triage the pull requests >> on GitHub, to help ensure that the pull requests are handled in a timely >> manner. I am also volunteerin

Re: [PHP-DEV] New Standardized HTTP Interface

Sherif Ramadan wrote on 31/10/2014 16:07: On Fri, Oct 31, 2014 at 11:56 AM, Rowan Collins mailto:rowan.coll...@gmail.com>> wrote: I think the piece that's missing is how exactly these interfaces would interact with core, or rather with the SAPIs which handle the actual transfer

[PHP-DEV] PHP 5.6.3 RC1 is ready for testing

Hello PHP 5.6.3 RC1 is available for testing. You can download it from http://server.famillecollet.com/php/ The Windows binaries are available at http://windows.php.net/qa/ This release contains a number of bugfixes. For the list of bugfixes that you can target in your testing, please refer to

[PHP-DEV] PHP 5.5.19 RC1 is ready for testing

Hello PHP 5.5.19 RC1 is available for testing. You can download it from http://server.famillecollet.com/php/ The Windows binaries are available at http://windows.php.net/qa/ This release contains a number of bugfixes. For the list of bugfixes that you can target in your testing, please refer t

Re: [PHP-DEV] New Standardized HTTP Interface

> On 31 Oct 2014, at 14:30, Sherif Ramadan wrote: > > To be perfectly clear, the default behavior would remain the same, so no PHP > app you have ever written would break. The difference is, you would now be > able to override any part of the default behavior by extending the > HttpRequest cl

Re: [PHP-DEV] New Standardized HTTP Interface

> On 30 Oct 2014, at 18:23, Sherif Ramadan wrote: > > I've started a draft RFC, but please be patient as this is a working in > progress, here https://wiki.php.net/rfc/http-interface on the wiki. > > The point here is to allow users to implement their own HttpRequest and > HttpResponse classes

Re: [PHP-DEV] New Standardized HTTP Interface

On 30 Oct 2014 19:03, "Sherif Ramadan" wrote: > > Hello Internals, > > I've been meaning to write up a full-blown RFC for introducing a new > standardized HTTP interface for PHP core for some time now. I figure now > with PHP 7 on the road map this might be a good time to start this > discussion s

Re: [PHP-DEV] [RFC] GitHub Pull Requests Triage Team

> On 30 Oct 2014, at 21:57, John Bafford wrote: > I would like to propose the creation of a team to triage the pull requests on > GitHub, to help ensure that the pull requests are handled in a timely manner. > I am also volunteering to lead such a team, should the RFC be approved. > > https://

Re: [PHP-DEV] [RFC] GitHub Pull Requests Triage Team

On Fri, Oct 31, 2014 at 3:13 PM, Florian Anderiasch wrote: > On 31.10.2014 09:58, Peter Cowburn wrote:> On 30 October 2014 21:57, > John Bafford wrote: > > > >> Hi, > >> > >> I would like to propose the creation of a team to triage the pull > requests > >> on GitHub, to help ensure that the pull

Re: [PHP-DEV] New Standardized HTTP Interface

On Fri, Oct 31, 2014 at 11:56 AM, Rowan Collins wrote: > > I think the piece that's missing is how exactly these interfaces would > interact with core, or rather with the SAPIs which handle the actual > transfer of HTTP requests and responses. > PHP would have an HttpRequest class, as noted in t

Re: [PHP-DEV] New Standardized HTTP Interface

Sherif Ramadan wrote on 31/10/2014 14:30: On Fri, Oct 31, 2014 at 5:25 AM, Andrea Faulds wrote: This is no less of a backwards-compatibility headache. This still breaks every PHP app I have ever written. To be perfectly clear, the default behavior would remain the same, so no PHP app you h

[PHP-DEV] Re: Native TLS

Matt Ficken in php.internals (Wed, 29 Oct 2014 21:53:08 -0700): >Anatol has been doing some great work with Thread Local Storage (under the >native-tls branch). > >I have tested it on Windows and its performance and functionality are now >the same as master builds (with phpng), though a few extensi

Re: [PHP-DEV] New Standardized HTTP Interface

On Fri, Oct 31, 2014 at 5:25 AM, Andrea Faulds wrote: > > > This is no less of a backwards-compatibility headache. This still breaks > every PHP app I have ever written. > > To be perfectly clear, the default behavior would remain the same, so no PHP app you have ever written would break. The dif

Re: [PHP-DEV] [RFC] GitHub Pull Requests Triage Team

On 31.10.2014 09:58, Peter Cowburn wrote:> On 30 October 2014 21:57, John Bafford wrote: > >> Hi, >> >> I would like to propose the creation of a team to triage the pull requests >> on GitHub, to help ensure that the pull requests are handled in a timely >> manner. I am also volunteering to lead s

Re: [PHP-DEV] Re: [RFC] Access to aliases definition by reflection

Dne 31.10.2014 12:00, Chris Wright napsal(a): I agree with Levi, this doesn't make a lot of sense. The only thing that would make sense in terms of supporting aliases for me would be this: getName()); // string(31) "Library\Http\Clients\CurlClient" Alias support is not needed here, HttpClient:

Re: [PHP-DEV] Re: [RFC] Access to aliases definition by reflection

On 31 October 2014 10:27, Miloslav Hůla wrote: > Dne 30.10.2014 14:50, Levi Morrison napsal(a): > >> I also don't think this feature is needed. In comments, simply use >> fully qualified names. >> > > FQN can be used in docblocks, that's true. But if you write some library > which uses annotation

Re: [PHP-DEV] Re: [RFC] Access to aliases definition by reflection

Dne 30.10.2014 14:50, Levi Morrison napsal(a): I also don't think this feature is needed. In comments, simply use fully qualified names. FQN can be used in docblocks, that's true. But if you write some library which uses annotations and you want to offer a kind of comfort to your users, your

Re: [PHP-DEV] New Standardized HTTP Interface

> On 31 Oct 2014, at 02:54, Sherif Ramadan wrote: > > So far there seems to be a lot of concern around BC, and particularly > removing or getting rid of GPC superglobals. So I completely understand the > concerns and hope to address them as clearly as possible. > > First, for the sake of BC I t

Re: [PHP-DEV] [RFC] GitHub Pull Requests Triage Team

On 30 October 2014 21:57, John Bafford wrote: > Hi, > > I would like to propose the creation of a team to triage the pull requests > on GitHub, to help ensure that the pull requests are handled in a timely > manner. I am also volunteering to lead such a team, should the RFC be > approved. > Slig

Re: [PHP-DEV] Volunteering for sysadmin help

Hello Chris, i think you have to use another mailing list: http://de2.php.net/mailing-lists.php There is a "PHP php.net internal infrastructure discussion" mailing list 2014-10-30 3:08 GMT+01:00 Chris Tankersley : > I've heard through grapevine that PHP was looking for some extra help with > so