Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:81341 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 56719 invoked from network); 28 Jan 2015 21:00:39 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Jan 2015 21:00:39 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.45 as permitted sender) X-PHP-List-Original-Sender: smalyshev@gmail.com X-Host-Fingerprint: 209.85.220.45 mail-pa0-f45.google.com Received: from [209.85.220.45] ([209.85.220.45:51919] helo=mail-pa0-f45.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C9/52-44076-6FD49C45 for ; Wed, 28 Jan 2015 16:00:38 -0500 Received: by mail-pa0-f45.google.com with SMTP id et14so29651031pad.4 for ; Wed, 28 Jan 2015 13:00:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=7BlOgkUtM+xDcHGNtX8Jk69B7i7cHaovSuxK/EXsbqk=; b=AAPQzZqPNVgHkeg+tq4sykJAh364qEeglPqmY9doggUv0h68tD+hbQoUkAXbamFHOE iTXmGc5r64RxPsNvn4L9C9aQxTmnrxWgv7xyxUqCFnAcZooJMv8FIJ/SuzhJMK/QERr3 e6SU7GaMNo52hezgTInG7GrFq7l7VDflt3fyMxB32J5EKLyIbOOAS5LdWWbtxqif216Z UO+C7rUIbYI1olFQFSM1acegTdBds7voskybpP++jZAPkHbGyPDz2I3smR3uFoI4rTtI gehZ+3xIy/FF34itpmCiUT8APkriDrNy93o4msRS3BFYxP/yDt935s2EKjV8xqxWppVP apjg== X-Received: by 10.69.31.170 with SMTP id kn10mr629700pbd.16.1422478835595; Wed, 28 Jan 2015 13:00:35 -0800 (PST) Received: from [192.168.2.145] (108-66-6-48.lightspeed.sntcca.sbcglobal.net. [108.66.6.48]) by mx.google.com with ESMTPSA id gi6sm5563218pbd.93.2015.01.28.13.00.34 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 28 Jan 2015 13:00:35 -0800 (PST) Message-ID: <54C94DF1.4030201@gmail.com> Date: Wed, 28 Jan 2015 13:00:33 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Michael Wallner CC: PHP Internals References: <54C8D36E.7010803@php.net> <54C94774.8000709@gmail.com> <54C94B2B.1050505@php.net> In-Reply-To: <54C94B2B.1050505@php.net> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] [VOTE] pecl_http From: smalyshev@gmail.com (Stanislav Malyshev) Hi! > I explained that in another mail and will put it (amongst a lot of other > things that came up during this thread) into the RFC: This is not enough. Saying "ZE APIs suck, so I implemented a bunch of my own and want to merge it in core because I like them" is not enough to make an informed decision - why ZE APIs suck? Can we fix them without introducing a bunch of new APIs? Are new APIs good for common case beyond this particular extension? It is not really feasible for each extension to use it's own API to deal with resources or objects. So if we introduce a new one, we should have clear understanding that a) existing ones are not enough and b) new one would serve more than narrow need of one case. > I'm a bad sales person, but I'll try better. The community needs to take an informed decision. For that, we need the information. You are the one who has the information, so please share it! It is obvious you think that what you did is good - otherwise you wouldn't propose it, and you probably know why exactly it is good - so please tell us so we'd know too. -- Stas Malyshev smalyshev@gmail.com