Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:81329
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.214 cause and error)
Message-ID: <54C93F46.8070005@lsces.co.uk>
Date: Wed, 28 Jan 2015 19:57:58 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <54C8D36E.7010803@php.net> <54C9338A.7020202@beccati.com> <54C9363D.6090102@php.net>
In-Reply-To: <54C9363D.6090102@php.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] [VOTE] pecl_http
From: lester@lsces.co.uk (Lester Caine)

On 28/01/15 19:19, Michael Wallner wrote:
>> Also, we're planning to move extensions from core to pecl, for example
>> > ext/mysql which I is still widely used by many applications, despite its
>> > known shortcomings. TBH, I don't see many reasons why a pecl extension
>> > should be moved to core.

> So that basically means, there shouldn't be any extension added to the
> core any more, or only PECL ones?

Bundling more and more into core is a pointless exercise. If pecl_http
is any good then it will gain it's own traction in distribution space as
just another package that can be added. Unbundling and better management
of interoperability is starting to see some more support and management
of extensions in their own code space is going to make life a lot easier
in the long term!

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk