Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:68417 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 50113 invoked from network); 8 Aug 2013 02:12:17 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 Aug 2013 02:12:17 -0000 Authentication-Results: pb1.pair.com header.from=yohgaki@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=yohgaki@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.177 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.217.177 mail-lb0-f177.google.com Received: from [209.85.217.177] ([209.85.217.177:40501] helo=mail-lb0-f177.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E6/38-06453-08EF2025 for ; Wed, 07 Aug 2013 22:12:16 -0400 Received: by mail-lb0-f177.google.com with SMTP id r11so2003557lbv.22 for ; Wed, 07 Aug 2013 19:12:13 -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=kQ3t/CgUJFxqiGmrJy287zA47YFBY4fuVfmFJwL1nK8=; b=UFVwN4e3NGfOW1uKLpiHMHnEa1R/lCgqpLQhrz93Iv5L3hiT0OPuCm+aCuslNn2bWr GHERxAm7oAhgmD7vq+VzFHCsv6+91ABmB3CLxvr3zUnh9Awz81nbY79Zr16a15kRT/T2 MPCc1NsBp27xLfwoqjDgjeZtQOsTaBRzNvGEmOmTFXPCVCXQYuCeop/4XpOYkRaH7oqI 4a2WLN9lxdbdACD4dNNfZJYocOKcxps0ZPX2mBCLEnJUfHDz5VsfD2h08KySmTztnf3n qZjNYaKya/U1vtD8K91gAxhfvDKV/q/Rs5O/OflPyMtz2w9OiEiZgT0RMggjZXbr3C/N aULw== X-Received: by 10.152.36.198 with SMTP id s6mr2623573laj.67.1375927933403; Wed, 07 Aug 2013 19:12:13 -0700 (PDT) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.112.127.233 with HTTP; Wed, 7 Aug 2013 19:11:33 -0700 (PDT) In-Reply-To: <5202FC8A.2070307@sugarcrm.com> References: <5202AF52.9060200@sugarcrm.com> <5202EE67.5020307@sugarcrm.com> <5202FC8A.2070307@sugarcrm.com> Date: Thu, 8 Aug 2013 11:11:33 +0900 X-Google-Sender-Auth: PjU5IYqsQlfPKqkrQRykERQhM68 Message-ID: To: Stas Malyshev Cc: "internals@lists.php.net" Content-Type: multipart/alternative; boundary=089e0160a9ccb507d404e3662f8c Subject: Re: [PHP-DEV] "php_serialize" session serialize handler From: yohgaki@ohgaki.net (Yasuo Ohgaki) --089e0160a9ccb507d404e3662f8c Content-Type: text/plain; charset=UTF-8 Hi Stas, On Thu, Aug 8, 2013 at 11:03 AM, Stas Malyshev wrote: > > Removing unneeded limitations, rather than forcing them to users, is user > > friendly and the way to go. IMHO. > > If we wrote it from scratch, sure. But if we already have existing and > working one, having people to deal with migrating data and > incompatibilities that arise IMHO is not worth the additional benefit of > having session variable named "!", without which one can live quite well. > So I'm not against having option for new serializer that does it if > somebody needs it, but I think changing the default for this and the > disruption potentially caused by it is not a very good idea. I agree. Breaking existing apps w/o good reason must be avoided. Therefore, I proposed that introduce new serializer for 5.5 as optional. Do you agree to have new serializer for 5.6 as optional and make it default for future releases? Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --089e0160a9ccb507d404e3662f8c--