The gain is that those without the extension can still unserialize the data and read it. It solves the problem discussed where older versions of PHP without IGBinary built in would be locked out from being able to unserialise data.
Didn't realise the reply was private. I did a reply-to-list, but Thunderbird picks up your address instead of internals. David On 23/08/11 09:52, Pierre Joye wrote: > then the gain will be zero. By the way, no need to go private to reply :) > > On Tue, Aug 23, 2011 at 1:29 AM, David Muir <davidkm...@gmail.com> wrote: >> That still requires the extension. I was referring to a userland >> implementation written in PHP, not C. >> >> Cheers, >> David >> >> On 22/08/11 17:21, Pierre Joye wrote: >>> PHP_FE(igbinary_serialize, arginfo_igbinary_serialize) >>> PHP_FE(igbinary_unserialize, >>> arginfo_igbinary_unserialize) >>> >>> On Mon, Aug 22, 2011 at 2:18 AM, David Muir <davidkm...@gmail.com> wrote: >>>> On 08/22/2011 10:07 AM, Pierre Joye wrote: >>>>> On Mon, Aug 22, 2011 at 1:49 AM, David Muir <davidkm...@gmail.com> wrote: >>>>> >>>>>> Why not provide a userland fallback? >>>>>> >>>>>> eg: /IGBinary/unserialize() >>>>>> >>>>>> It could unserialize the string, albeit slowly, but still give you >>>>>> access to the data without needing the extension. At least that way you >>>>>> have something rather than nothing. >>>>> igbinary has functions for that already. >>>>> >>>> It does? I didn't see it in the docs, or in the git tree. >>>> >>>> Cheers, >>>> David >>>> >>> >> > > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
