Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:76701
Return-Path: <mike.php.net@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 85781 invoked from network); 19 Aug 2014 12:19:54 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 19 Aug 2014 12:19:54 -0000
Authentication-Results: pb1.pair.com header.from=mike.php.net@gmail.com; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=mike.php.net@gmail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.182 as permitted sender)
X-PHP-List-Original-Sender: mike.php.net@gmail.com
X-Host-Fingerprint: 209.85.217.182 mail-lb0-f182.google.com  
Received: from [209.85.217.182] ([209.85.217.182:35611] helo=mail-lb0-f182.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 4A/B0-16275-8E043F35 for <internals@lists.php.net>; Tue, 19 Aug 2014 08:19:53 -0400
Received: by mail-lb0-f182.google.com with SMTP id z11so5406140lbi.13
        for <internals@lists.php.net>; Tue, 19 Aug 2014 05:19:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:sender:in-reply-to:references:date:message-id:subject
         :from:to:cc:content-type;
        bh=OyZS86BExKeP8k3bWiQ0raftTgm5MoZwUdDAbo9itEE=;
        b=xeEVwYlX5rFe6W7j+esYPP+cnmbWJ7Ah5AgPruArscwikPYHrTDTfNQh10KqKnYh8Y
         FhghzQEda1Utyz6FAj96Ihyj16MgfAyX5fioqZFB4+FHQ4M/gb08KPchirVGkXe5JKzg
         RwgpnedDG0jPIe0woJRlXp3e439WCmRxJUt3VAC2oxGIwqZ0PQIMG4m7oispLtC173wH
         +M+n8ezJ/THcPpBbmZKRKcID5spxrT3iyi0w9Tp89batVUngAtfLS2+hc8WpT2k4C1vH
         uUpSHGU0lJXi7otuQ1ODmQVFVQ/in1sCpU760eIRaSnOJo+/aaP+boF19/MeKorDK5Fj
         V8tg==
MIME-Version: 1.0
X-Received: by 10.112.118.68 with SMTP id kk4mr23033314lbb.4.1408450789971;
 Tue, 19 Aug 2014 05:19:49 -0700 (PDT)
Sender: mike.php.net@gmail.com
Received: by 10.114.48.66 with HTTP; Tue, 19 Aug 2014 05:19:49 -0700 (PDT)
In-Reply-To: <CAEZPtU4bijwCYpih+vMYimXb4zJM1W0K5pvmdr+a4zZgUo2zDA@mail.gmail.com>
References: <53F3018E.6090201@php.net>
	<2d56v912urnaoilcckvkvhu1th6k4ntt1c@4ax.com>
	<CAEZPtU4bijwCYpih+vMYimXb4zJM1W0K5pvmdr+a4zZgUo2zDA@mail.gmail.com>
Date: Tue, 19 Aug 2014 14:19:49 +0200
X-Google-Sender-Auth: nMzi9gD4u7BbUixRxRXd6VKPIPw
Message-ID: <CALJZF3jajjfxhVgRcc8LDtJAkZ3--Rkp=q7EamXxXOav3Dd6eA@mail.gmail.com>
To: Pierre Joye <pierre.php@gmail.com>
Cc: Jan Ehrhardt <phpdev@ehrhardt.nl>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7bb03ee2051d240500fa81b8
Subject: Re: [PHP-DEV] Re: [RFC] pecl_http
From: mike@php.net (Michael Wallner)

--047d7bb03ee2051d240500fa81b8
Content-Type: text/plain; charset=UTF-8

On 19 August 2014 11:24, Pierre Joye <pierre.php@gmail.com> wrote:

> On Tue, Aug 19, 2014 at 11:17 AM, Jan Ehrhardt <phpdev@ehrhardt.nl> wrote:
> > Is pecl_http v2 still dependent on propro and raphf? If so, they should
> > be in core as well.
> >
>
> I never really understood why they are needed or why they have been
> splitted off. I can imagine that other exts may need a similar thing
> but...
>

To be reusable. pecl/raphf is also used by pecl/pq; peck/propro has not had
another use case yet, though.

-- 
Regards,
Mike

--047d7bb03ee2051d240500fa81b8--