Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103198
MIME-Version: 1.0
References: <5518056b-150f-517c-2c24-09d5da4414f0@gmx.de> <d290481d-be6c-3dea-2054-a486e37c1231@php.net>
 <3a3a59bf-98a3-764d-def2-e514f506edfc@gmail.com> <2e82ff1a-7045-3b7e-3feb-bfdac29883e9@gmx.de>
 <2f30a0da-c15a-8723-bebd-4143d49cf032@gmail.com> <d20a72fa-656a-b528-90f7-63f631aded87@gmx.de>
 <7fbac401-d15f-e7fe-2792-41f5c8cea411@gmail.com>
In-Reply-To: <7fbac401-d15f-e7fe-2792-41f5c8cea411@gmail.com>
Date: Thu, 20 Sep 2018 13:08:28 +0200
Message-ID: <CAF+90c9UXA5jfYHKZtsBeMDMsA-E-fh6hYtjowbhGQaoj0PsGA@mail.gmail.com>
To: Stanislav Malyshev <smalyshev@gmail.com>
Cc: Christoph Becker <cmbecker69@gmx.de>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000a9020005764b8b96"
Subject: Re: [PHP-DEV] [RFC} Deprecate and Remove ext/wddx
From: nikita.ppv@gmail.com (Nikita Popov)

--000000000000a9020005764b8b96
Content-Type: text/plain; charset="UTF-8"

On Wed, Sep 19, 2018 at 12:24 AM Stanislav Malyshev <smalyshev@gmail.com>
wrote:

> Hi!
>
> > Hmm, I have some doubts that it's okay for users if we remove the WDDX
> > extension in PHP 7.4 without any deprecation phase.  Is there any
>
> I think deprecation phase is necessary for features that are being
> removed. For extension being moved to PECL I do not see any point in
> annoying the users for a year with error messages. If they need it,
> they'll keep using it anyway, if they do not, they'll drop it - but
> deprecation messages here do not add much value that one single
> announcement can't make.
>
> > Furthermore, the deprecation notices *are* annoying, and it seems to me
> > that is good, because probably nobody should continue to use these
> > functions.  They're unsafe for general data change, and there are likely
>
> Well, if we think nobody should use them then it's not move to PECL,
> it's discontinuation of the extension. These two are completely
> different cases.
>
> > Don't get me wrong: I like to unbundle the WDDX extension with the least
> > possible effort as soon as possible, but dropping it appears to be
> > simpler as possible.
>
> If it's still available in PECL, whoever needs it would easily get it
> there. If we think it's unusable anymore, then we need to declare that
> and not move it to PECL but sunset it.
>

We have deprecated and moved to PECL a number of extensions in the recent
past. These were mysql and ereg in PHP 7.0 and mcrypt in PHP 7.2. I have
always understood these moves as "sunsetting" the extensions, in the sense
of strongly discouraging their continued use, as well as removing any
promise of further maintenance. The move to PECL rather than outright
deletion of the code is just a matter of general policy (or so I thought).

Especially for an extension such as ext/wddx where we have legitimate
security concerns, just moving it off to PECL without any deprecation
warnings would send the wrong kind of signal. I would prefer it to stick
the the same process we have used for other extensions in the past (i.e.
first deprecate everything and then archive it in PECL.)

Regards,
Nikita

--000000000000a9020005764b8b96--