Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:81328
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.44 as permitted sender)
Sender: Michael Wallner <mike.php.net@gmail.com>
Message-ID: <54C93D29.8070303@php.net>
Date: Wed, 28 Jan 2015 20:48:57 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Andrea Faulds <ajf@ajf.me>
CC: Levi Morrison <levim@php.net>, 
 PHP Internals <internals@lists.php.net>
References: <54C8D36E.7010803@php.net> <CAFMT4NpjFSycCVrSUfBBgfJEJv=4Yw8cpmQ-45JWf=75ptr8Lg@mail.gmail.com> <CAFMT4NqUU21HGuOf1qZiHP8MvzG4q=o8G99UN5ushLZLh3ydtg@mail.gmail.com> <584E167F-CD06-4ACB-A33A-92DD178BCFD8@ajf.me> <54C934C1.6080601@php.net> <32FA0837-DCDD-4157-AD1A-3A9DE91B5FFB@ajf.me>
In-Reply-To: <32FA0837-DCDD-4157-AD1A-3A9DE91B5FFB@ajf.me>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] [RFC] [VOTE] pecl_http
From: mike@php.net (Michael Wallner)

On 28/01/15 20:18, Andrea Faulds wrote:
> Hi Michael,
> 
>> On 28 Jan 2015, at 19:13, Michael Wallner <mike@php.net> wrote:
>> 
>> - Client
>> 
>> The http stream wrapper is a hack and the existing libcurl binding
>> is subpar. They could be improved separately, but that is not
>> subject of this RFC.
>> 
>> Currently only libcurl is implemented as a provider for the client 
>> functionality. Provides most of the functionality of current
>> libcurl. Representation of the request and response how a client
>> sees them. Support for parallel requests and optional libev{,ent}
>> support.
> 
> If the client is merely a wrapper around cURL, what benefit does it
> offer over ext/curl except a better API?
> 
> Personally, I’ve never liked that PHP requires cURL for doing HTTP
> requests. It’s a language made for the web, it should have built-in
> HTTP, and it should share code between its server-side HTTP and
> client-side HTTP stuff. I don’t think that the HTTP stream wrappers
> are a “hack” - they’re what PHP should have had all along. I think we
> should focus on improving them (so there’s no need to use cURL)
> rather than adding yet another HTTP client.

Sounds a bit like NIH.
We could implement a http_client driver with the code from the stream
wrapper and see how they compare in feature set and performance.

-- 
Regards,
Mike