Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:81066
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.47 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
In-Reply-To: <CAGa2bXZN67hw_hLH7uWdYmMWKdNyxKUeAzrX1K+d3jiie4MZRg@mail.gmail.com>
References: <CAGa2bXZN67hw_hLH7uWdYmMWKdNyxKUeAzrX1K+d3jiie4MZRg@mail.gmail.com>
Date: Sat, 24 Jan 2015 11:36:27 +0900
Message-ID: <CAGa2bXb_y4EOpBhRUo6+b6C9dVZCezjQnFiSHbQ8LsNo5MD+7Q@mail.gmail.com>
To: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c2cc9a091412050d5cc806
Subject: Re: User defined session serialize handler
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--001a11c2cc9a091412050d5cc806
Content-Type: text/plain; charset=UTF-8

Hi all,

Additional comments.

On Sat, Jan 24, 2015 at 11:28 AM, Yasuo Ohgaki <yohgaki@ohgaki.net> wrote:

> php.ini :
>  There is "session.serialize_handler" (Default: php) "user" will be added,
> but user must use
>  session_set_serialize_handler() just like session_set_save_handler().
>
> 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.
>

php_serialize uses plain PHP serialize/unserialize for $_SESSION. i.e.
Serialized data is the same
as serialize($_SESSION).  php_serialize is introduced from PHP 5.5.

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--001a11c2cc9a091412050d5cc806--