Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:54688 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 70511 invoked from network); 18 Aug 2011 13:42:22 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Aug 2011 13:42:22 -0000 Authentication-Results: pb1.pair.com header.from=johannes@schlueters.de; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=johannes@schlueters.de; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error) X-PHP-List-Original-Sender: johannes@schlueters.de X-Host-Fingerprint: 217.114.211.66 config.schlueters.de Received: from [217.114.211.66] ([217.114.211.66:60322] helo=config.schlueters.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 76/93-50449-DB61D4E4 for ; Thu, 18 Aug 2011 09:42:22 -0400 Received: from [192.168.2.230] (ppp-93-104-44-22.dynamic.mnet-online.de [93.104.44.22]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by config.schlueters.de (Postfix) with ESMTPSA id B2CB377CF6; Thu, 18 Aug 2011 15:42:17 +0200 (CEST) To: Ferenc Kovacs Cc: Paul Dragoonis , Roger Llopart Pla , Arpad Ray , PHP Internals List In-Reply-To: References: <1313673396.1489.6.camel@guybrush> Content-Type: text/plain; charset="UTF-8" Date: Thu, 18 Aug 2011 15:42:16 +0200 Message-ID: <1313674936.1489.11.camel@guybrush> Mime-Version: 1.0 X-Mailer: Evolution 2.30.2 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Activation of IGBinary serialization extension in 5.4 by default From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=) On Thu, 2011-08-18 at 15:33 +0200, Ferenc Kovacs wrote: > we already do this (session.serialize_handler, defaults to our own > format, but can be set to wddx or igbinary) Well the session handler doesn't matter too much and is more of an admin thing, unlike serialize()/unserialize(). Those are the ones which shouldn't be set by configuration as they are used programmatically. The format is relevant for session though, too, as people use memcache or something to share sessions from multiple hosts. > and I really hate that the php session format is almost compatible > with serialize/unserialize. if I remember correctly only lacks the > a:number_of_items_in_the_session:{} around the session data. > why did we did this? to save a few bytes? /o\ History with register globals, back then each variable had to be serialized individually based on the list of registered vars. We resisted from changing the format to keep compatibility. (some people also want to stay sessions alive while updating) johannes