Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:68408 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 30763 invoked from network); 8 Aug 2013 00:58:55 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 Aug 2013 00:58:55 -0000 Authentication-Results: pb1.pair.com smtp.mail=yohgaki@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=yohgaki@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.180 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.217.180 mail-lb0-f180.google.com Received: from [209.85.217.180] ([209.85.217.180:33989] helo=mail-lb0-f180.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 6C/D3-06453-E4DE2025 for ; Wed, 07 Aug 2013 20:58:55 -0400 Received: by mail-lb0-f180.google.com with SMTP id a16so1972202lbj.25 for ; Wed, 07 Aug 2013 17:58:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=psyVdsipZrkzbwMuUBI8pbA251tH4PNoFl/yoT1Z+2Y=; b=O+fyeqr0ef+6FvjHkdGjxgwCokvdnBOz6LV4ZZ0ruLYGCm4J8mVGUXZVOCdJyYSXBK qImnISsGL+iL6diDWqx1FtunHsyGRU9ZIJd/h7h/c4pqmMAzniSSk+D2fiUqkLXmhG0s r1I3uDy43f0oTDnbOe/9avLUbpX1DZwyJL3oP1kvpF0Bw8SOOn5IjyKKcI4aMaHnzjfO HE+jum5j3SlC3Chexx39vJFuG1kt4H8s3arOMovAKMFJlRoJB8ARRSAnfIwJzeaObQsW RRVhVGU6Ahr6QUHi2tF97dtgH2BJpXSDfOeqiztFVqKPd9BENacSg7HYC8KC3TbCWsek rMVA== X-Received: by 10.112.219.102 with SMTP id pn6mr1302429lbc.18.1375923531371; Wed, 07 Aug 2013 17:58:51 -0700 (PDT) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.112.127.233 with HTTP; Wed, 7 Aug 2013 17:58:11 -0700 (PDT) In-Reply-To: <5202AF52.9060200@sugarcrm.com> References: <5202AF52.9060200@sugarcrm.com> Date: Thu, 8 Aug 2013 09:58:11 +0900 X-Google-Sender-Auth: 5zbjuFR4Bt6et00YCob0cqEnzFE Message-ID: To: Stas Malyshev Cc: "internals@lists.php.net" Content-Type: multipart/alternative; boundary=001a11c3ca14535d6e04e365298d Subject: Re: [PHP-DEV] "php_serialize" session serialize handler From: yohgaki@ohgaki.net (Yasuo Ohgaki) --001a11c3ca14535d6e04e365298d Content-Type: text/plain; charset=UTF-8 Hi Stas, On Thu, Aug 8, 2013 at 5:34 AM, Stas Malyshev wrote: > Why is it useful to do this? I don't see how using numerical indexes in > global namespace (and SESSION is one of global namespaces in PHP) is a > good idea. Could you explain the use case here? > Personally, I would not use numeric index. However, users are expecting it to work and there is no way to raise informative error message where is wrong. IIRC, there were description about "register_globals" originated limitations in our documents, but it seems it was gone already. > This seems to be to be of a very limited use and introducing new > serializer format with all resulting BC problems and confusion doesn't > seem to be worth it. > The limitation is come from register_globals and it has nasty problem. i.e. Error occurred at unknown script line 0. This kind of behavior is better to be removed and it's worth it. IMHO. Most users don't care what serializer does and users who may have BC issue can use old serializers anytime. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --001a11c3ca14535d6e04e365298d--