Hi!
> PHP Session,
http://php.net/manual/en/session.configuration.php#ini.session.serialize-handler
?
> Memcache, Redis, etc - not configuring custom serializer.
>
Not sure about those, but don't see a problem adding custom handler.
--
Stas Malyshev
smalys...@gmail.com
--
PHP Internals -
2017-06-29 2:13 GMT+03:00 Stanislav Malyshev :
> 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
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 ca
2017-06-28 11:04 GMT+02:00 Rasmus Schultz :
> Back in 2014 there was an informal proposal on the mailing list to replace
> PHP serialization with an efficient binary (msgpack) format.
>
> https://www.mail-archive.com/internals@lists.php.net/msg69870.html
>
> As argued back then, breaking serialize
> -Oorspronkelijk bericht-
> Van: Rasmus Schultz [mailto:ras...@mindplay.dk]
> Verzonden: woensdag 28 juni 2017 11:04
> Aan: PHP internals
> Onderwerp: [PHP-DEV] Binary (msgpack) serialize/unserialize
> 1. adopt msg_pack() and msg_unpack() from the PECL package as standa
Back in 2014 there was an informal proposal on the mailing list to replace
PHP serialization with an efficient binary (msgpack) format.
https://www.mail-archive.com/internals@lists.php.net/msg69870.html
As argued back then, breaking serialize() and unserialize() is unacceptable
for many reasons.
