Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:40787
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain smashlabs.com from 67.15.58.61 cause and error)
Message-ID: <48E10C0D.3010307@smashlabs.com>
Date: Mon, 29 Sep 2008 12:10:37 -0500
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.9) Gecko/20061207 Thunderbird/1.5.0.9 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: Michael Wallner <mike@php.net>
CC: internals@lists.php.net
References: <19.DC.27717.E51E7D84@pb1.pair.com>	 <48DAC68D.5070607@chiaraquartet.net> <7dd2dc0b0809241632n72f0e91w1db0c697bfad984f@mail.gmail.com> <001301c91eab$5b282bd0$11788370$@ca> <48DB2EAC.4090809@sci.fi> <8C.C1.19781.863BCD84@pb1.pair.com>
In-Reply-To: <8C.C1.19781.863BCD84@pb1.pair.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: Adding pecl/http to core
From: ralph@smashlabs.com (Ralph Schindler)

Mike,

I have a few questions about the API and target use cases.  What is the 
best medium to ask these questions and document them?  This thread 
certainly is not the best place im sure of.

Thanks,
Ralph

Michael Wallner wrote:
> Jani Taskinen wrote:
> 
>> So pecl/http is actually ext/curl with OO API?
> 
> Not really. libcurl is not HTTP only, pecl/http utilizes libcurl for
> it's HTTP request functionality. pecl/http also provides much improved
> HTTP response and zlib functionality besides an "swizz-army-knife" for URLs.
> 
>> Why not merge the two then..? Or rather, replace ext/curl with pecl/http
>> once latter has BC API for us non-oo folks out there..
> 
> You don't have to write OO code to use pecl/http, neither do you
> have the possibility to query any protocol other than HTTP with 
> pecl/http.
> 
> Regards,
> Mike
>