Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:81295 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 20605 invoked from network); 28 Jan 2015 09:49:25 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Jan 2015 09:49:25 -0000 Authentication-Results: pb1.pair.com smtp.mail=mike.php.net@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=mike.php.net@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.52 as permitted sender) X-PHP-List-Original-Sender: mike.php.net@gmail.com X-Host-Fingerprint: 74.125.82.52 mail-wg0-f52.google.com Received: from [74.125.82.52] ([74.125.82.52:38173] helo=mail-wg0-f52.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id CA/4C-45774-F90B8C45 for ; Wed, 28 Jan 2015 04:49:20 -0500 Received: by mail-wg0-f52.google.com with SMTP id y19so19476677wgg.11 for ; Wed, 28 Jan 2015 01:49:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=N/Synm71+HZzF+albVdkOe8mrieJ+aQRrwhQYJndbmk=; b=oFemCqAS8m13Fy7Z/GU1tD/UlAMVCRrIgVHqWFdwmDbBgLZbOPt5oe1xCCnhLl31P3 yn5+YTNL8/b3sM2JP0qkHqrJYO3cU6oHeDHOUuRvup85S3Hz5tkmhQpSriHQxVZCP1Av XpM6IAcAMwuP8HFhwzCI+W68ceXrgJWJGyn6Hg+SmZf/FbdkJkx8pTRRtQKUe/UWKX3L U8qQG/5yL7hdNaGeQlHVPs2wWwNzWr5dfOOhxs7j38KFW/ozylkf0e9LxW+v7VT8BWrD hsKuGJwuKlbZ+fvPOFSc5lbYZQRS4WSN7HdsTSgT8gneqkdKcXKVIQ9nPq2wz2aTPVyL eTpA== X-Received: by 10.194.103.228 with SMTP id fz4mr5611014wjb.82.1422438556770; Wed, 28 Jan 2015 01:49:16 -0800 (PST) Received: from [192.168.2.120] (89-104-28-113.customer.bnet.at. [89.104.28.113]) by mx.google.com with ESMTPSA id ez1sm5304552wjd.31.2015.01.28.01.49.14 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 28 Jan 2015 01:49:14 -0800 (PST) Sender: Michael Wallner Message-ID: <54C8B099.1040409@php.net> Date: Wed, 28 Jan 2015 10:49:13 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Pierre Joye CC: PHP Internals References: <54C1261D.7080009@php.net> <21F16F7C-CEBE-4498-A539-E2E66EE147F7@php.net> In-Reply-To: <21F16F7C-CEBE-4498-A539-E2E66EE147F7@php.net> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] pecl_http From: mike@php.net (Michael Wallner) On 23/01/15 09:27, Michael Wallner wrote: > >> On 23 01 2015, at 02:40, Pierre Joye wrote: >> >> On Thu, Jan 22, 2015 at 5:32 PM, Michael Wallner >> wrote: >>> Hi! >>> >>> Now, that I'm mostly done with porting pecl/http [1] and >>> dependencies (propro [2] and raphf [3]) to ZE3 I'd like to >>> restart discussion on the topic, whether it is feasible to add >>> pecl_http as a bundled extension to the core. >>> >>> https://wiki.php.net/rfc/pecl_http >>> [...] >> By the way, I did not yet look more deeply to raphf and propro but >> that's something I like to discuss. If their feautures are useful >> for other parts of the core, extensions, bundled or not, we should >> consider moving them to the main APIs and not as two new >> independent extensions. >> [...] > I think a short discussion about where to put the dependant code and > noting the outcome in the RFC could be the way to go. I guess just a > few people who think that pecl_http is about to be included would > suffice. I just pushed a tree with pecl/http merged to ext/http, pecl/propro merged to ext/standard and pecl/raphf merged to main/. https://github.com/m6w6/php-src/tree/merge-http -- Regards, Mike