Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:81078
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.174 as permitted sender)
User-Agent: K-9 Mail for Android
In-Reply-To: <CAGa2bXZN67hw_hLH7uWdYmMWKdNyxKUeAzrX1K+d3jiie4MZRg@mail.gmail.com>
References: <CAGa2bXZN67hw_hLH7uWdYmMWKdNyxKUeAzrX1K+d3jiie4MZRg@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain;
 charset=UTF-8
Date: Sat, 24 Jan 2015 15:42:26 +0000
To: Yasuo Ohgaki <yohgaki@ohgaki.net>,"internals@lists.php.net" <internals@lists.php.net>
Message-ID: <4775CF59-9190-4706-A09F-BCF4E798A76F@gmail.com>
Subject: Re: [PHP-DEV] User defined session serialize handler
From: rowan.collins@gmail.com (Rowan Collins)

On 24 January 2015 02:28:07 GMT, Yasuo Ohgaki <yohgaki@ohgaki.net> wrote:
>I also would like to php_serialize handler as the default serializer
>and
>make php/php_binary deprecated.
>
>php/php_binary serializers are made to work with register_globals and
>have
>many limitations.
>e.g. Integer key not allowed, key cannot start with number, delimiter
>chars
>are invalid and
>ignored, etc. php_serialize does not have such limitations at all.

I'm in favour of this part. In the unlikely event that someone needs to access the same session data with PHP 5 and 7, they should be able to switch back to the old format, but for most users, plain serialise is a much more sensible format.

An additional problem with the existing format is that there are no functions to work with it outside of the $_SESSION array, so you can't just unserialize a local copy.

Regards,
-- 
Rowan Collins
[IMSoP]