Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:68456 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 85568 invoked from network); 8 Aug 2013 22:31:48 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 Aug 2013 22:31:48 -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.45 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.215.45 mail-la0-f45.google.com Received: from [209.85.215.45] ([209.85.215.45:41026] helo=mail-la0-f45.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 59/02-06453-35C14025 for ; Thu, 08 Aug 2013 18:31:47 -0400 Received: by mail-la0-f45.google.com with SMTP id fj20so2563118lab.4 for ; Thu, 08 Aug 2013 15:31:44 -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=KMAIDtZLZMS/H+n1GqPPHxnJNse5v4ME2sh3jIQmfNs=; b=vRsQdDXlpzrELHNe1HKk49X9Z0wHg15kvakL0wPXxwmTcXS1F+/1E71DTnZL72mixb s9fakkLs5Q++Bk1Qf+rTz+ZKenfZwDYSqwaBP6H4BZ+/mp9c3cZ9jwFPhT6oA8RBjncz jzhszvjiBtlvOm+QlOLjW2bhKuLqyLeXtwn6lhKgKeMtE/OfqHj9muRMwZyonf9eARjp 4hzgCHg7zm5oV0Thgy4xePaHroomOIFp1km30HCntvfiZ3kAwF8D5gMEhXRidZoV5hXW DjTWm+RH6dUNfefKoOstPWU5FUi5Mjdcvb1hg+By6tPSOh4aUwVGQvSK8CrlIiaeV6dV DKmw== X-Received: by 10.152.36.198 with SMTP id s6mr4674855laj.67.1376001104481; Thu, 08 Aug 2013 15:31:44 -0700 (PDT) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.112.127.233 with HTTP; Thu, 8 Aug 2013 15:31:03 -0700 (PDT) In-Reply-To: <52038ABF.8060904@lsces.co.uk> References: <5202AF52.9060200@sugarcrm.com> <5202EE67.5020307@sugarcrm.com> <5202FC8A.2070307@sugarcrm.com> <52035622.1090301@lsces.co.uk> <52038ABF.8060904@lsces.co.uk> Date: Fri, 9 Aug 2013 07:31:03 +0900 X-Google-Sender-Auth: KnOZGxhcew_CuazAO2ZuEfQU09U Message-ID: To: Lester Caine Cc: "internals@lists.php.net" Content-Type: multipart/alternative; boundary=089e0160a9cc0b131404e377393a Subject: Re: [PHP-DEV] "php_serialize" session serialize handler From: yohgaki@ohgaki.net (Yasuo Ohgaki) --089e0160a9cc0b131404e377393a Content-Type: text/plain; charset=UTF-8 Hi, On Thu, Aug 8, 2013 at 9:10 PM, Lester Caine wrote: > Leigh wrote: >> >> I can't judge the scope of the break, or how many users will be affected. >> I >> just want to say that breaks without a good reason shouldn't happen. >> > > Seconded. > > In hindsight I personally would have preferred to remain with clean PHP5.2 > code and should have carried on with that. I've wasted many many months > reworking everything for PHP5.4 and so I'm now at a stage where my real > answer is probably "Do what you like, I'll stick with and maintain PHP5.4 > now". The problem is that ISP's like Go Daddy will still switch versions > without any regard to users as they have just done with Apache 2.4 so we > all end up having to live with other peoples decisions :( I still have > sites where 'register_globals' is on simply because I've not had any time > to rework perfectly functional systems and I can avoid anybody else > changing the infrastructure! Nobody will pay for changing those sites ... I think you are confused. How php_serialize would cause BC issues for PHP users? Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --089e0160a9cc0b131404e377393a--