Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:68419 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 53288 invoked from network); 8 Aug 2013 02:24:16 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 Aug 2013 02:24:16 -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.215.47 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.215.47 mail-la0-f47.google.com Received: from [209.85.215.47] ([209.85.215.47:59125] helo=mail-la0-f47.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FC/E8-06453-05103025 for ; Wed, 07 Aug 2013 22:24:16 -0400 Received: by mail-la0-f47.google.com with SMTP id eo20so1695804lab.6 for ; Wed, 07 Aug 2013 19:24: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=I8VMdwJbtQp3dBu2HuJ683n9DydF5NLcAqhL97E07R0=; b=oxPJK+StUotrJ4NfHp4laysBmHP2q4+8hURJVJE8kazc50I9Np7V/gscXF5fs0E8H7 vS6x3e8JlHA4rmmjI7AFi7dUltv1Cuxk8xBX3e9q0wBer64f80wvpjZQ0sdskvVvrxiK y/gIqXkcEYS6rak6ZdQI2u5AYgO1Zhdk9ICjjNEKXamlV8tC12pzz+c075rt2WL8PUDi msAN91y52oB3t/X1mpY5DJqBoN1jECe8ZTydN5WhrfiNfah91rT1OeQVwhYGWUwdryZ3 ZPzbX4JIhgMmfmboc5xcSApwIfxn6YBt2KPPLNlkdnbOzl2eJ5P4/Muxa3FT+BNk1jH3 KgFw== X-Received: by 10.112.136.195 with SMTP id qc3mr1350141lbb.55.1375928653176; Wed, 07 Aug 2013 19:24:13 -0700 (PDT) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.112.127.233 with HTTP; Wed, 7 Aug 2013 19:23:33 -0700 (PDT) In-Reply-To: References: <5202AF52.9060200@sugarcrm.com> <5202EE67.5020307@sugarcrm.com> <5202FC8A.2070307@sugarcrm.com> Date: Thu, 8 Aug 2013 11:23:33 +0900 X-Google-Sender-Auth: AlQKv8SoqmrxWf4WB_9zY4DdQtU Message-ID: To: Stas Malyshev Cc: "internals@lists.php.net" Content-Type: multipart/alternative; boundary=089e011770db9be6c004e3665aee Subject: Re: [PHP-DEV] "php_serialize" session serialize handler From: yohgaki@ohgaki.net (Yasuo Ohgaki) --089e011770db9be6c004e3665aee Content-Type: text/plain; charset=UTF-8 Hi Stas, On Thu, Aug 8, 2013 at 11:11 AM, Yasuo Ohgaki wrote: > 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? > Or make it optional for 5.5 and 5.6, write full documentation about serializer and make new serializer default for future releases. It would work better. There would be enough time for users may have BC issue. If they do, it would be simple task to adopt because it is plain serialize(). What do you think? -- Yasuo Ohgaki yohgaki@ohgaki.net --089e011770db9be6c004e3665aee--