Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:68437
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.26.187 cause and error)
Message-ID: <52038ABF.8060904@lsces.co.uk>
Date: Thu, 08 Aug 2013 13:10:39 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:22.0) Gecko/20100101 Firefox/22.0 SeaMonkey/2.19
MIME-Version: 1.0
To: "internals@lists.php.net" <internals@lists.php.net>
References: <CAGa2bXbn_U9GBnskNwdJqDzFpBXeucT-Q7SoQ3hmQ59u-6=KDw@mail.gmail.com>	<5202AF52.9060200@sugarcrm.com>	<CAGa2bXbgm4qDrO-3h=A3X75qo6B-Jf5dNORBFEC49p7JtFStGA@mail.gmail.com>	<5202EE67.5020307@sugarcrm.com>	<CAGa2bXYr3neNJg7fATdLH3V-qc2rDHbVKg2AzOsaU0LjWa3iuw@mail.gmail.com>	<5202FC8A.2070307@sugarcrm.com>	<CAGa2bXYdwZLfadyNm+mUpw9mHmQS9Ybh013hs73CMW=e-UnwxA@mail.gmail.com>	<CAGa2bXbUD7sDAteUFncw6gYVjN4etw1fPT0eDK3CAXrEzc-oWA@mail.gmail.com>	<52035622.1090301@lsces.co.uk>	<CAGa2bXaHyONvikGLvuNLxPJ9nrtqs=HxXcFJJg5_raC5tyF70A@mail.gmail.com>	<CAPwsocHeQxiwhCE5=4S5ii9vZy8KmU9XCLRrRgA0MnZf0G67vQ@mail.gmail.com>	<CAGa2bXY9+raaFikqpbWFwgUvOxeQr7naPXR92s9HXsRiPXdmbw@mail.gmail.com>	<CAPwsocFL=pBc_KEZ3hFjTjpaXxF5HHGzy8V8_WUYa8+SpX0oKw@mail.gmail.com>	<CAGa2bXbywtEyPmE-G4TDk-ofWAXpK-sL18AanJ40Bmq-9vAokg@mail.gmail.com> <CAPwsocGf6L2a1+iQq6-HXTAwE5Gv_HtFnUS8_6s-1XA3nin5Fw@mail.gmail.com>
In-Reply-To: <CAPwsocGf6L2a1+iQq6-HXTAwE5Gv_HtFnUS8_6s-1XA3nin5Fw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] "php_serialize" session serialize handler
From: lester@lsces.co.uk (Lester Caine)

Leigh wrote:
> On 8 August 2013 12:05, Yasuo Ohgaki<yohgaki@ohgaki.net>  wrote:
>
>> >What's the point of having old serialzers that is bonded to
>> >"register_globals"?
>> >This kind of change should have done when 5.4.0 was released, IMO.
>> >
> Because somebodies code will depend on functionality not changing, and we
> shouldn't break their code without a very good reason.
>
> 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 ...

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk