Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:81334 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 41676 invoked from network); 28 Jan 2015 20:30:27 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Jan 2015 20:30:27 -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.41 as permitted sender) X-PHP-List-Original-Sender: smalyshev@gmail.com X-Host-Fingerprint: 209.85.220.41 mail-pa0-f41.google.com Received: from [209.85.220.41] ([209.85.220.41:35885] helo=mail-pa0-f41.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F4/FE-44076-0E649C45 for ; Wed, 28 Jan 2015 15:30:26 -0500 Received: by mail-pa0-f41.google.com with SMTP id kq14so29395595pab.0 for ; Wed, 28 Jan 2015 12:30:19 -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=mgtJ6Iau8miZ9UyLCRI19NJu+7ilCWxZkB/ySTjwhAk=; b=C0acLZOImn72BjoaJz6uaFIl2QfTt0lpSz/Uu38HllBpwcaUzddaYW2RLN10tMp82N BwR+RRdHb4UjGPp+8Ux14UeHVT/kRyj94aNSRX+vpLetlPaw8YR66UmYKX5s1DUnQHwc jonOfKTh+X2aTkD9DYbjNYMBMlU4iK4FOnna/xjVXhqpz1qjbZlkBGQSCYIsKkettq9X 4bljTyXWHgos6KJMCCjYpu4CxVmioH72AUnyo29k1/Du5KX37li0FcPh/Dn4fI0SU0Iq eCE1AJ2lK3PxPmtnvI+HgZPaDuEgncwbL4oUOskLcu2jTX2+tbkxlozK+9Z05qKRhhJH IEVw== X-Received: by 10.66.132.44 with SMTP id or12mr8929987pab.42.1422477019804; Wed, 28 Jan 2015 12:30:19 -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 vk4sm5547354pbc.74.2015.01.28.12.30.18 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 28 Jan 2015 12:30:19 -0800 (PST) Message-ID: <54C946D9.1030004@gmail.com> Date: Wed, 28 Jan 2015 12:30:17 -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: Andrea Faulds , Michael Wallner CC: Levi Morrison , PHP Internals References: <54C8D36E.7010803@php.net> <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: smalyshev@gmail.com (Stanislav Malyshev) Hi! > 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 I see no problem in depending on cURL. NIH'ing every part of the software universe in unfeasible, and if somebody does this one job and does it well - why not use it? We don't have enough resources here to implement every detail of the huge protocol like HTTP, and that's the whole point of opensource to reuse and combine projects. > 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 HTTP stream wrappers work for some cases, but not for all and for cases where you need deep involvement with details of HTTP - like headers, byteranges, content encodings, etc. - they might not be the best API to deal with it. -- Stas Malyshev smalyshev@gmail.com