Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:99671
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.178 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <831f345f-6d6a-9d9b-e691-c92c49cfefed@gmail.com>
References: <CADqTB_hcMd8O0S9oT8QNUFuYnpscx0579Ofj59Vop=Q1YEj0eQ@mail.gmail.com>
 <831f345f-6d6a-9d9b-e691-c92c49cfefed@gmail.com>
Date: Thu, 29 Jun 2017 11:36:49 +0300
Message-ID: <CALW=WEDXYiUpx8-8X1DoUxn_Vdqn5-+yeb_torm19wcQK-iNug@mail.gmail.com>
To: Stanislav Malyshev <smalyshev@gmail.com>
Cc: Rasmus Schultz <rasmus@mindplay.dk>, PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] Binary (msgpack) serialize/unserialize
From: ua.san.alex@gmail.com ("S.A.N")

2017-06-29 2:13 GMT+03:00 Stanislav Malyshev <smalyshev@gmail.com>:
> Hi!
>
>> Back in 2014 there was an informal proposal on the mailing list to replace
>> PHP serialization with an efficient binary (msgpack) format.
>
> Why replace? If you have it as an extension, can't people that want to
> use it just use it?
>
> I'm still not sure why we need to do anything in core that can't be done
> in an extension. Is there some handler missing that doesn't allow to use
> custom serializer in some scenario?

PHP Session, Memcache, Redis, etc - not configuring custom serializer.