Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:68465
Return-Path: <lester@lsces.co.uk>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 43595 invoked from network); 9 Aug 2013 10:07:26 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 9 Aug 2013 10:07:26 -0000
Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown
Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.26.188 cause and error)
X-PHP-List-Original-Sender: lester@lsces.co.uk
X-Host-Fingerprint: 213.123.26.188 c2beaomr10.btconnect.com  
Received: from [213.123.26.188] ([213.123.26.188:24296] helo=mail.btconnect.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 73/C8-06453-D5FB4025 for <internals@lists.php.net>; Fri, 09 Aug 2013 06:07:26 -0400
Received: from host81-159-192-145.range81-159.btcentralplus.com (EHLO linux-dev4.lsces.org.uk) ([81.159.192.145])
	by c2beaomr10.btconnect.com
	with ESMTP id MJI47813;
	Fri, 09 Aug 2013 11:07:22 +0100 (BST)
Message-ID: <5204BFBB.9030505@lsces.co.uk>
Date: Fri, 09 Aug 2013 11:08:59 +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: PHP internals <internals@lists.php.net>
References: <CAGa2bXbn_U9GBnskNwdJqDzFpBXeucT-Q7SoQ3hmQ59u-6=KDw@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> <52038ABF.8060904@lsces.co.uk> <CAGa2bXabMOJUR6_PO-AgEQ4SKSnG5F-gQrOFeF7U=66LyuYn=w@mail.gmail.com> <CAPwsocEesVo23dFrut0gT8p=Bp8SraEAZAD61qKUPW6FGZ783A@mail.gmail.com> <5204B690.4060006@lsces.co.uk> <CAGa2bXbLFzDkW834gTM=G8rDXOk47Z_AO1B6eRpNT_vRMWq5CA@mail.gmail.com>
In-Reply-To: <CAGa2bXbLFzDkW834gTM=G8rDXOk47Z_AO1B6eRpNT_vRMWq5CA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Mirapoint-IP-Reputation: reputation=Good-1,
	source=Queried,
	refid=tid=0001.0A0B0302.5204BF59.0028,
	actions=tag
X-Junkmail-Premium-Raw: score=7/50,
	refid=2.7.2:2013.8.9.92741:17:7.944,
	ip=81.159.192.145,
	rules=__MOZILLA_MSGID,
		__HAS_MSGID,
		__SANE_MSGID,
		__HAS_FROM,
		__USER_AGENT,
		__MOZILLA_USER_AGENT,
		__MIME_VERSION,
		__TO_MALFORMED_2,
		__BOUNCE_CHALLENGE_SUBJ,
		__BOUNCE_NDR_SUBJ_EXEMPT,
		__SUBJ_ALPHA_END,
		__IN_REP_TO,
		__CT,
		__CT_TEXT_PLAIN,
		__CTE,
		__ANY_URI,
		__URI_NO_MAILTO,
		__URI_NO_WWW,
		__CP_URI_IN_BODY,
		__SUBJ_ALPHA_NEGATE,
		BODY_ENDS_IN_URL,
		BODYTEXTP_SIZE_3000_LESS,
		BODY_SIZE_800_899,
		__MIME_TEXT_ONLY,
		RDNS_GENERIC_POOLED,
		HTML_00_01,
		HTML_00_10,
		BODY_SIZE_5000_LESS,
		RDNS_SUSP_GENERIC,
		BODY_SIZE_1000_LESS,
		RDNS_SUSP,
		BODY_SIZE_2000_LESS,
		BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2beaomr10.btconnect.com
X-Junkmail-Signature-Raw: score=unknown,
	refid=str=0001.0A0B0204.5204BF5B.0024,ss=1,re=0.000,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0,
	ip=0.0.0.0,
	so=2011-07-25 19:15:43,
	dmn=2013-04-19 10:07:54,
	mode=multiengine
X-Junkmail-IWF: false
Subject: Re: [PHP-DEV] "php_serialize" session serialize handler
From: lester@lsces.co.uk (Lester Caine)

Yasuo Ohgaki wrote:
> If users aren't reading release note of minor version up, then it is users' fault,
> not ours. If it is, we cannot release new PHP.

MANY users don't even know that their hosting has been changed until their sites 
stop working ... This happens a lot more often now than it ever used to!
Silly little things like '<?=' stopping working took a lot of time to address 
because the 'problem' was not easy to spot. Blaming the users is simply not 
acceptable!

-- 
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