Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110124
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: "Christoph M. Becker" <cmbecker69@gmx.de>,
 PHP internals <internals@lists.php.net>
References: <eed5338f-020b-a977-ba16-1adeb860f7c5@gmx.de>
 <882bb1d5-fd8d-f3ad-85cf-58fa6feec41d@gmx.de>
 <81cc5e5f-e084-fedd-f178-dc675c324ded@telia.com>
 <CAF+90c_vnP19GJSZsR6RUgxSfjy+779QW=LotP9d_3xd67XHhQ@mail.gmail.com>
Message-ID: <ee77b4c4-80ce-5365-81bb-ac274adf2d9f@telia.com>
Date: Mon, 11 May 2020 11:30:45 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:68.0) Gecko/20100101
 Thunderbird/68.8.0
MIME-Version: 1.0
In-Reply-To: <CAF+90c_vnP19GJSZsR6RUgxSfjy+779QW=LotP9d_3xd67XHhQ@mail.gmail.com>
Content-Type: multipart/alternative;
 boundary="------------198A98CD7BA2A6A7283B9460"
Content-Language: en-GB
Subject: Re: [PHP-DEV] Re: [RFC] Unbundle ext/xmlrpc
From: bjorn.x.larsson@telia.com (=?UTF-8?Q?Bj=c3=b6rn_Larsson?=)

--------------198A98CD7BA2A6A7283B9460
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Den 2020-05-11 kl. 11:16, skrev Nikita Popov:
> On Mon, May 11, 2020 at 11:00 AM Björn Larsson 
> <bjorn.x.larsson@telia.com <mailto:bjorn.x.larsson@telia.com>> wrote:
>
>     Den 2020-05-11 kl. 08:57, skrev Christoph M. Becker:
>
>     > On 26.04.2020 at 15:28, Christoph M. Becker wrote:
>     >
>     >> I propose to unbundle ext/xmlrpc, and written a respective RFC:
>     >>
>     >> <https://wiki.php.net/rfc/unbundle_xmlprc>
>     > Thanks for the feedback so far.  Unless there are further issues
>     > regarding the RFC to be discussed, I'll open voting tomorrow.
>     >
>     > Thanks,
>     > Christoph
>
>     For sure it makes sense to unbundle it! However, I recall the
>     discussion
>     that was held around unbundling of ext/wddx that was about PECL
>     becoming a graveyard for unmaintained extensions. Is any of that
>     also applicable here, e.g. secondary voting option?
>
>     - https://externals.io/message/103164#103209
>
>
> To be clear, the secondary voting option you're suggesting is whether 
> to deprecate the extension in PECL?
>
> I believe the RFC already addresses the question, and I agree with the 
> reasoning where. Unlike the move of wddx to PECL, which was partially 
> made because we had specific security concerns with the extension, our 
> primary concern here is maintenance. There does not seem to be a 
> strong need to signal that people should stop using it ASAP. The 
> extension (and more importantly, the underlying library) has been 
> unmaintained for many years already and the move to PECL will not 
> change things materially in that regard.
>
> Nikita

That was exactly my concern, i.e. to deprecate it or not. I was
seeing deprecation also as a signal about quality, not just if
there was a security issue. OTOH, maybe that's obvious when
looking at the changelog in the future.

r//Björn L



--------------198A98CD7BA2A6A7283B9460--