Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:68470 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 16861 invoked from network); 9 Aug 2013 21:28:27 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Aug 2013 21:28:27 -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.43 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.215.43 mail-la0-f43.google.com Received: from [209.85.215.43] ([209.85.215.43:52836] helo=mail-la0-f43.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 68/76-06453-AFE55025 for ; Fri, 09 Aug 2013 17:28:26 -0400 Received: by mail-la0-f43.google.com with SMTP id ep20so1863730lab.2 for ; Fri, 09 Aug 2013 14:28:23 -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=uh0um9g60ZtzZdUFuAOj0oDeqMMcvGdDFtT16ZpU1Po=; b=frhGqEhdC2uIMZc6HyVpXXenqWUZ2pfOVHE5MK0D/e+RDVnyf1HfMkZEFA9C/xuv1X IZzZQhaW1dh2ZahuwrGdjToH0Pb4pxZwhxi1o2mDC9BOdl+TAspj1A4xdXSruVebDZwv ESa7EDe0ST17v7KVpJm5bPlmjuaVdVT5mFWXAtnmYcNXfmS/Ek1efWEjtxNNrikloDRc vovHIrZuGpYX7bA+XfswTvLlO6phBoqDVAcOODOT3BJDqsJvTllZ1uAnNUAJrud6tYAt xYFo8KGAv9HMubjed+VD/TFFTEHTyk037zMgzP9Gm+9RBBDjIedgtNdfZMV7g+kyxFFu cwaA== X-Received: by 10.152.37.41 with SMTP id v9mr1010704laj.9.1376083703519; Fri, 09 Aug 2013 14:28:23 -0700 (PDT) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.112.127.233 with HTTP; Fri, 9 Aug 2013 14:27:43 -0700 (PDT) In-Reply-To: <52051E71.9010309@sugarcrm.com> References: <5202FC8A.2070307@sugarcrm.com> <52035622.1090301@lsces.co.uk> <52038ABF.8060904@lsces.co.uk> <5204B690.4060006@lsces.co.uk> <52051E71.9010309@sugarcrm.com> Date: Sat, 10 Aug 2013 06:27:43 +0900 X-Google-Sender-Auth: gqbYBEn4QWizzF6Q83i7FjayWDk Message-ID: To: Stas Malyshev Cc: Lester Caine , PHP internals Content-Type: multipart/alternative; boundary=089e0160b998545f8104e38a741c Subject: Re: [PHP-DEV] "php_serialize" session serialize handler From: yohgaki@ohgaki.net (Yasuo Ohgaki) --089e0160b998545f8104e38a741c Content-Type: text/plain; charset=UTF-8 Hi Stas, On Sat, Aug 10, 2013 at 1:53 AM, Stas Malyshev wrote: > We can also take some responsibility for making it easier to > upgrade > That's the reason why I proposed adding "php_serialize" to 5.5. Even if there are very few users may have problem with new serializer, it would be good to provide enough time to play with it. Adding "php_serialize" does not affect users at all unless they explicitly use it. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.netHi --089e0160b998545f8104e38a741c--