Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:58838 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 43761 invoked from network); 10 Mar 2012 18:22:45 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 10 Mar 2012 18:22:45 -0000 X-Host-Fingerprint: 217.114.211.68 unknown Date: Sat, 10 Mar 2012 13:22:44 -0500 Received: from [217.114.211.68] ([217.114.211.68:14434] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 60/42-32413-4FB9B5F4 for ; Sat, 10 Mar 2012 13:22:44 -0500 To: internals@lists.php.net References: User-Agent: slrn/0.9.9p1 (SunOS) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: X-Posted-By: 217.114.211.68 Subject: Re: Upgrade cURL extension From: dsp@php.net (David Soria Parra) On 2012-03-10, Pierrick Charron wrote: > --047d7b2ee19338d79004bae668f3 > Content-Type: text/plain; charset=ISO-8859-1 > > Hi all, > > As you may know, the cURL PHP extension is currently not in sync > (featurewise) with the original libcurl. I started to work on it to > make it as close as possible from the original libcurl. I also did > some cleaning to make it easier to maintain (ordered all the > constants/features by their libcurl version). All those changes were > made on the trunk branch only. > > I wanted to make this new version available in PHP5.4 but > unfortunately I did finish my work when it was already in RC phase. > The question now is should we include this new version in PHP5.4.1 or > should we wait for PHP 5.5/6/7 or whatever PHP next will be. There is > no feature break (AFAIK) so all the previous code should work as > expected. You'll find the list of new features attached and the last > code in the trunk branch. Hi Pierrick, as long as your implementation does not contain crucial security fixes, I prefer not having it in 5.4 Let's try to keep 5.4 as stable as possible and minimize the amount of new code.