Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:68461 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 23904 invoked from network); 9 Aug 2013 08:28:08 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Aug 2013 08:28:08 -0000 Authentication-Results: pb1.pair.com header.from=leight@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=leight@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.182 as permitted sender) X-PHP-List-Original-Sender: leight@gmail.com X-Host-Fingerprint: 74.125.82.182 mail-we0-f182.google.com Received: from [74.125.82.182] ([74.125.82.182:33102] helo=mail-we0-f182.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 41/C5-06453-718A4025 for ; Fri, 09 Aug 2013 04:28:07 -0400 Received: by mail-we0-f182.google.com with SMTP id u55so3347155wes.27 for ; Fri, 09 Aug 2013 01:28:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=lMN6KQTCUejg2vkJSewCYwb+G3Eh3LAyiyDwEfuvFJs=; b=Fnd6hpLEeorF+B2XIQgnJveyyIKAWR187mCOYVylaDMtoH1wNJ0tenzWd4JRhceyNm nHPFcxQLiiPD52I/rRPIVxLAE5EIBujQNGYZNN9r6w5iYw8GKAFTgJgANuKko9JCsITc HqFs3kB3fUSiekshwSYs4rdkh9z+Ywrb6dsZgbVta29sX93GuN1lR28ul+x7wiYhvfkK Uivfkyi/EOBMyKfckUoa/Fh9GpahyTnFgL0GuNgraR46nLNjSdGZqBr56Z618P5YmREl UClqly94NW5nV7QvHm1uLz35wxlYNbicwvB7TpnAHaxGhb8Z8XT1HbJXNdaM9yo1fQdC nN4A== MIME-Version: 1.0 X-Received: by 10.180.13.43 with SMTP id e11mr1501879wic.21.1376036884290; Fri, 09 Aug 2013 01:28:04 -0700 (PDT) Received: by 10.216.182.193 with HTTP; Fri, 9 Aug 2013 01:28:04 -0700 (PDT) In-Reply-To: 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 09:28:04 +0100 Message-ID: To: Yasuo Ohgaki Cc: Lester Caine , "internals@lists.php.net" Content-Type: multipart/alternative; boundary=001a11c24762afa2f704e37f8dd8 Subject: Re: [PHP-DEV] "php_serialize" session serialize handler From: leight@gmail.com (Leigh) --001a11c24762afa2f704e37f8dd8 Content-Type: text/plain; charset=ISO-8859-1 On 8 August 2013 23:31, Yasuo Ohgaki wrote: > > How php_serialize would cause BC issues for PHP users? > Not everyone uses PHP in the way you would expect. Just how many sites out there do you think use PHPs session functionality? I'd go for hundreds of millions, and that's a pretty big target to hit. If you session_encode() something on 5.x with default settings and 5.x+1 cannot session_decode() it with default settings, that is a BC break. --001a11c24762afa2f704e37f8dd8--