Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:54683
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAKxcST-n_aC1NJ8pLg5natwRRcxEHV_t-fiEhYX4mc=G7WPFaA@mail.gmail.com>
References: <CAKxcST-n_aC1NJ8pLg5natwRRcxEHV_t-fiEhYX4mc=G7WPFaA@mail.gmail.com>
Date: Thu, 18 Aug 2011 14:22:35 +0200
Message-ID: <CAEZPtU5R9MdFjUkzyyyt57_ZnM=QkiT-_Fcntqjmyd7pGy5xkA@mail.gmail.com>
To: Paul Dragoonis <dragoonis@gmail.com>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] Activation of IGBinary serialization extension in 5.4
 by default
From: pierre.php@gmail.com (Pierre Joye)

hi!

On Thu, Aug 18, 2011 at 1:12 PM, Paul Dragoonis <dragoonis@gmail.com> wrote:

> After a brief discussion with Pierre I'm taking this discussion to here.

For the record here, I'm not in favor of bundling igbinary (or other
custom serializer). My main concerns are:

 . the PHP serializer can be overridden at runtime (as in after the build)
 . there will always have some new faster, better, sexier serializer,
depending on the app/usages
 . we can't enable it by default (as other stated too here) for BC
reason (and interop)
 . not enabling it by default defeats the purpose of bundling it
 . easier to support it while being only in pecl ('do you use the core
version or latest pecl?")


Cheers,
-- 
Pierre

@pierrejoye | http://blog.thepimp.net | http://www.libgd.org