On Fri, Aug 19, 2011 at 12:36 PM, Pierre Joye <[email protected]> wrote:
> On Fri, Aug 19, 2011 at 1:28 PM, Sebastian Bergmann <[email protected]>
> wrote:
> > Am 18.08.2011 13:12, schrieb Paul Dragoonis:
> >> Here we get a great perf boost, and what's more excellent as we don't
> have
> >> to break BC to get there!
> >
> > Are you sure it does not break BC? Does http://bit.ly/nIRxqz still work
> > with IGBinary, for instance?
>
> That obviously won't work as long as igbinary is used. It is covered
> by the "interop" or BC break parts in my initial reply.
>
So far, it looks like this "transparent" upgrade isn't that transparent
anymore and will result in BC breaks. New approaches must be thought of.
Like Pierre said, there will be new serialization engines in the future so
it makes no sense to add more functions like serialize_binary() or whatnot.
I think we need to keep our code base identical and maintain the
serialize_handler via our php.ini configuration.
Cheers,
Paul.
>
> Cheers,
> --
> Pierre
>
> @pierrejoye | http://blog.thepimp.net | http://www.libgd.org
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>