Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:64482 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 10716 invoked from network); 2 Jan 2013 18:25:16 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 2 Jan 2013 18:25:16 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 67.192.241.163 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 67.192.241.163 smtp163.dfw.emailsrvr.com Linux 2.6 Received: from [67.192.241.163] ([67.192.241.163:51816] helo=smtp163.dfw.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id AD/8C-12868-B8B74E05 for ; Wed, 02 Jan 2013 13:25:16 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp26.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id C9A81802C4; Wed, 2 Jan 2013 13:25:12 -0500 (EST) X-Virus-Scanned: OK Received: by smtp26.relay.dfw1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id EFA59802DA; Wed, 2 Jan 2013 13:25:11 -0500 (EST) Message-ID: <50E47B87.5030307@sugarcrm.com> Date: Wed, 02 Jan 2013 10:25:11 -0800 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: =?UTF-8?B?Sm9oYW5uZXMgU2NobMO8dGVy?= CC: Pierrick Charron , Internals References: <4F5C5540.8010204@sugarcrm.com> <4F5D3569.8050307@sugarcrm.com> <50DE4A01.8050006@sugarcrm.com> <50E3DEA8.3090509@sugarcrm.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] CURL file posting From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > What I wonder about in this thread: If we struggle here why not take > the full step and abstract curl details comletely away and provide > something like pecl/http by default instead? curl extension is widely used. So suggesting we just throw it away makes no sense to me. We need to fix this deficiency in the API, since it may break applications and expose users to hard-to-track security holes. As for developing other extensions and adding pecl/http by default, this is a valid issue but I'd rather discuss it separately. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227