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<array...@gmail.com> wrote:
Hi,
On Thu, Aug 18, 2011 at 12:12 PM, Paul Dragoonis<dragoo...@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.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
