Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:53225
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Thu, 09 Jun 2011 14:11:41 -0400
Message-ID: <29.10.00968.DDC01FD4@pb1.pair.com>
To: internals@lists.php.net
References: <8757232E56758B42B2EE4F9D2CA019C901499F97@US-EX2.zend.net>
	<BANLkTikau4c4-HzkGAXG15AMS2tr6fe+NA@mail.gmail.com>
	<4DEB6A80.9030406@thelounge.net>
User-Agent: Pan/0.134 (Wait for Me; GIT cb32159 master)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] Bundling "modern" extensions
From: mike@php.net (Michael Wallner)

On Sun, 05 Jun 2011 13:37:36 +0200, Reindl Harald wrote:
> http://pecl.php.net/package/pecl_http/2.0.0dev1 coll, in th emiddle of
> 5.3 lifecycle a total incompatible reqrite is started and hopefully no
> one has projects relying on the pecl-extension

In the past many developers did not feel comfy enough with the pecl_http 
extension.  It had been proposed for inclusion in the core distribution 
for a few times, but people always had doubts about the API etc.

I started the rewrite of the extension, because it had one really big 
drawback, namely that message bodies where implemented as memory chunk 
instead of streams.  The next major headache caused the confusion which 
the HttpResponse class was responsible for.  Another major addition will 
be the choice of request handling library http\Request should use. 
libcurl, neon and serf are on the table currently.

Anyway, if people want to take part in architecting the future of this 
extension, they are more than welcome.

I already invited you to participate, but you did not answer.

Mike