Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:81013
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.44 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <54C1261D.7080009@php.net>
References: <54C1261D.7080009@php.net>
Date: Fri, 23 Jan 2015 02:40:56 +0100
Message-ID: <CAEZPtU6HE6cf38xPpS6M9QvP_f7jrcK5Aka=1mJKPh30eb36Lg@mail.gmail.com>
To: Michael Wallner <mike@php.net>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [RFC] pecl_http
From: pierre.php@gmail.com (Pierre Joye)

On Thu, Jan 22, 2015 at 5:32 PM, Michael Wallner <mike@php.net> wrote:
> Hi!
>
> Now, that I'm mostly done with porting pecl/http [1] and dependencies
> (propro [2] and raphf [3]) to ZE3 I'd like to restart discussion on the
> topic, whether it is feasible to add pecl_http as a bundled extension to
> the core.
>
> https://wiki.php.net/rfc/pecl_http
>
> [1] https://github.com/php/pecl-http-pecl_http/tree/phpng
> [2] https://github.com/php/pecl-php-propro/tree/phpng
> [3] https://github.com/php/pecl-php-raphf/tree/phpng
>
> For a test run with master, clone into ext/ and `configure --with-http
> --enable-propro --enable-raphf` after buildconf.
>
> Let me know if it doesn't work out of the box for you.
>
> I'll have to update the corresponding links in the RFC to the phpng
> branches and refresh the code coverage reports in the next few days.
>
> Reminder!
>
> Do not look at php.net/http; API docs are here:
> http://devel-m6w6.rhcloud.com/mdref/http/

I am still all for it :)

By the way, I did not yet look more deeply to raphf and propro but
that's something I like to discuss. If their feautures are useful for
other parts of the core, extensions, bundled or not, we should
consider moving them to the main APIs and not as two new independent
extensions.

-- 
Pierre

@pierrejoye | http://www.libgd.org