Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:68415
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.178 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
In-Reply-To: <5202EE67.5020307@sugarcrm.com>
References: <CAGa2bXbn_U9GBnskNwdJqDzFpBXeucT-Q7SoQ3hmQ59u-6=KDw@mail.gmail.com>
 <5202AF52.9060200@sugarcrm.com> <CAGa2bXbgm4qDrO-3h=A3X75qo6B-Jf5dNORBFEC49p7JtFStGA@mail.gmail.com>
 <5202EE67.5020307@sugarcrm.com>
Date: Thu, 8 Aug 2013 10:41:43 +0900
Message-ID: <CAGa2bXYr3neNJg7fATdLH3V-qc2rDHbVKg2AzOsaU0LjWa3iuw@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a1133c6900597f504e365c5e6
Subject: Re: [PHP-DEV] "php_serialize" session serialize handler
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--001a1133c6900597f504e365c5e6
Content-Type: text/plain; charset=UTF-8

Hi Stas

On Thu, Aug 8, 2013 at 10:03 AM, Stas Malyshev <smalyshev@sugarcrm.com>wrote:

> > Personally, I would not use numeric index.
> > However, users are expecting it to work and there is no way to raise
>
> I don't think it is reasonable to expect it to work, it never worked, it
> never was documented to work and there's no real use case for it.


I also think this limitation was documented, but it seems it gone (or
I missed)

 > The limitation is come from register_globals and it has nasty problem.
>
> I don't see how is it a nasty problem if there's actually no good reason
> to do this. If there is a good reason to do it, please tell what it is.


PHP Notice: Unknown: Skipping numeric key 1 in Unknown on line 0
https://bugs.php.net/bug.php?id=65359

This error occurs at shutdown. Removing unneeded limitation is good reason
IMHO. If there is

$_SESSION[$key] = $var;

It's very hard to find what is and where is wrong.


> > Most users don't care what serializer does and users who may have
> > BC issue can use old serializers anytime.
>
> Using old serializer is work which we would make users do for
> improvement that practically nobody needs and that does not provide any
> actual improvement that can not easily be achieved otherwise. Breaking
> BC just because somebody somewhere needs an exotic feature that can
> easily be worked around doesn't look like a good idea to me.


I should have mentioned that new serializer not only allow numeric index,
but
also allow special characters due to the implementation. i.e. ! and | may
be
used with the new serializer.

Removing unneeded limitations, rather than forcing them to users, is user
friendly and the way to go. IMHO.

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--001a1133c6900597f504e365c5e6--