Hi Levi, > On 28 Jan 2015, at 17:53, Levi Morrison <le...@php.net> wrote: > >> >> Discussion has been very low on this topic since it was proposed on >> August 19th, so I just opened the vote on the RFC whether to add >> pecl_http to the core. The vote will be open until about 12:00 UTC on >> Friday, February 6th. >> >> https://wiki.php.net/rfc/pecl_http#vote > > > I wish you had pinged the list before opening the vote. I know there were a > few people who wanted to make comments but have just been very busy. For > example, I have been dealing with the return types RFC which has soaked up > all of the time I have for working on PHP projects. > > Some feedback: I feel the RFC is not clear about the advantages and > disadvantages of including this package. Mostly, the RFC is "hey I have > this package can we include it in core?" I feel like it's fairly incomplete > as to *why* we should include it. There is a fair amount of work done in > user-land for these types of utilities, and I think without a more balanced > discussion we'd be giving this extension a distinct advantage. > > If we allow it to remain in voting phase despite these issues, I have to > vote no simply because I don't feel like there is enough information > presented in the RFC for anyone except current pecl_http users to make a > good decision; that's hardly a good situation for the language as a whole.
I completely agree here: reading the RFC I have little idea as to: * What pecl/http actually is * What pecl/http does * How what pecl/http does differs from PHP’s existing facilities * Why PHP should include pecl/http * Why PHP should enable pecl/http by default As it stands, I can’t see how it’s substantially different from our existing stuff in core, except maybe more OOP and a little more feature-complete. I’ve sort of gleaned this from looking at pecl/http’s docs… the RFC is barren, lacking in details about anything. It really doesn’t make any case for itself, and I’m also concerned about possibly unnecessary implementation duplication. PHP already has several implementations of various aspects of the HTTP protocol, the RFC doesn’t explain why we need another. So, like you, I’m probably going to vote No. Thanks. -- Andrea Faulds http://ajf.me/ -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
