Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:66894 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 2601 invoked from network); 3 Apr 2013 02:19:42 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 3 Apr 2013 02:19:42 -0000 Authentication-Results: pb1.pair.com smtp.mail=laruence@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=laruence@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.43 as permitted sender) X-PHP-List-Original-Sender: laruence@gmail.com X-Host-Fingerprint: 209.85.215.43 mail-la0-f43.google.com Received: from [209.85.215.43] ([209.85.215.43:47746] helo=mail-la0-f43.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FB/94-07534-BB19B515 for ; Tue, 02 Apr 2013 21:19:39 -0500 Received: by mail-la0-f43.google.com with SMTP id ek20so980636lab.2 for ; Tue, 02 Apr 2013 19:19:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=FaSQWCPcir4TSeaLn/gVgeXA6hUzi3v5JuT37IfnCdA=; b=mqdyZPzmSypbOVSfnYItzqs9+lDiMQTD76MggKbGIq5dR3NKR8+MjKaSBMAO1sCZYb Yos+ZLAPr722kSVwWFSr+d0x0WtWOOID/QgVfY70L9/KRlPVgSS8NeEV7ihUicqRFYGW y6hsNbOKQpBCONS4R+lMcGkViAfzHFNODKK0pPD0jOM0fEixLwAVUSPLS86SX9ihSs4C F1Su3Y8nz/Tz1OjTQv3JvKbx7ASeXFt/Lj2C3ebjDBJW7BmzDeJcGgLSp8IrVlPzvoVO J9DBhpMkpjjb2Ey6+OxhIXkeM2H1A3sDQu1BQheApeO6arTufXoe5JywXqfJznMiiNCB SXFg== X-Received: by 10.112.125.232 with SMTP id mt8mr91562lbb.110.1364955576439; Tue, 02 Apr 2013 19:19:36 -0700 (PDT) MIME-Version: 1.0 Sender: laruence@gmail.com Received: by 10.114.66.196 with HTTP; Tue, 2 Apr 2013 19:19:16 -0700 (PDT) In-Reply-To: References: Date: Wed, 3 Apr 2013 10:19:16 +0800 X-Google-Sender-Auth: NJ9_0VzWv-uNQwMMFrdNDTlvf2Y Message-ID: To: Hannes Magnusson Cc: PHP Internals Content-Type: multipart/alternative; boundary=089e01160d60449bfe04d96b7cae Subject: Re: [PHP-DEV] Add a constant to reflect --with-curlwrappers From: laruence@php.net (Laruence) --089e01160d60449bfe04d96b7cae Content-Type: text/plain; charset=UTF-8 Added new constant CURL_WRAPPERS_ENABLE in (include 5.4) https://github.com/php/php-src/commit/d7f709a032a40cb475042b43db07a4698a2488b7 thanks On Mon, Apr 1, 2013 at 9:53 PM, Laruence wrote: > > > > On Mon, Apr 1, 2013 at 7:18 AM, Hannes Magnusson < > hannes.magnusson@gmail.com> wrote: > >> On Sun, Mar 31, 2013 at 6:25 AM, Laruence wrote: >> > Hey: >> > >> > there are some issues when people run some codes in a php which is >> > compiled with --with-curlwrappers, like #61336, or the recently test >> script >> > for #64433 (failed when curl wrappers enabled). >> > >> > I know, that the curl wrapper should act the same as php http >> wrapper, >> > but for now, we need to provide the ability to user, that they can warn >> if >> > they codes can not run with curl wrappers.. >> > >> > here are some really usages: >> > https://github.com/UnionOfRAD/lithium/issues/59 and >> > http://weizhifeng.net/wrong-with-curlwrappers.html >> > >> > I propose to add a constant : bool CURL_WRAPPERS_ENABLE >> >> The curl wrappers have always been a major pain, with plenty of bugs >> and we tend to forget to add context options there to match the >> standard wrapper on new feature. >> >> It has been marked as experimental since forever, and I think its time >> to face the failed experiment and remove it. >> > > Hey: > > remove is also okey for me, but, I think it probably can only happen in > 5.6 > > before that, I think a flag to 5.4+ is a good choice :) > > thanks > >> >> -Hannes >> > > > > -- > Laruence Xinchen Hui > http://www.laruence.com/ > -- Laruence Xinchen Hui http://www.laruence.com/ --089e01160d60449bfe04d96b7cae--