Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:54682
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain kingsquare.nl from 212.54.42.164 cause and error)
Message-ID: <4E4CFF4B.5010901@kingsquare.nl>
Date: Thu, 18 Aug 2011 14:02:19 +0200
Organization: Kingsquare Information Services
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <CAKxcST-n_aC1NJ8pLg5natwRRcxEHV_t-fiEhYX4mc=G7WPFaA@mail.gmail.com> <CA+p1TcZ07HVpQn7YZngsREYtV-gbtQAPg8Ou4HyVuxE36Pnj7A@mail.gmail.com> <CAH-PCH6WN=iEdSob0wTy43MRY4aK8AqpmOgJxWS_U5mc0w1Jjg@mail.gmail.com>
In-Reply-To: <CAH-PCH6WN=iEdSob0wTy43MRY4aK8AqpmOgJxWS_U5mc0w1Jjg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Activation of IGBinary serialization extension in 5.4
 by default
From: robin@kingsquare.nl ("Kingsquare.nl - Robin Speekenbrink")

Hello everyone,

My first post after watching the list for a while: my opionion on this 
would also be incorporate it into the core but with BC compatibility: 
the serializer could (easily from what i understand) check to see if the 
serialized format is in the `old` format and read that accordingly, but 
write it back in the new... That way the problem would 'clear' itself up.. ?

(or is this just simple 'user'-level thinking? :P)

With kind regards,

Robin Speekenbrink
Kingsquare Information Services

Op 18-8-2011 13:48, Ferenc Kovacs schreef:
> On Thu, Aug 18, 2011 at 1:30 PM, Arpad Ray<arraypad@gmail.com>  wrote:
>> Hi,
>>
>> On Thu, Aug 18, 2011 at 12:12 PM, Paul Dragoonis<dragoonis@gmail.com>  wrote:
>>> Hey guys,
>>>
>>> After a brief discussion with Pierre I'm taking this discussion to here.
>>> We have the igbinary pecl extension available [1], however not many of our
>>> userbase are familiar that it even exists.
>>> Here [2] is the performance boost we get from using igbinary with
>>> serialize() and unserialize().
>>>
>>> Here we get a great perf boost, and what's more excellent as we don't have
>>> to break BC to get there!
>>
>> It would break BC for anyone with serialized strings stored in the
>> current format.
>>
>> Maybe bundle it in core and provide an ini setting like
>> session.serialize_handler, but I don't think making it the default in
>> 5.4 is an option.
>
> agree with the BC part, just wanted to mention that that igbinary can
> already be set as a session handler via session.serialize_handler if
> the extension present.
>