Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:77567
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAPwsocH32Wc0U-xyWDYdCar1rf+bSK3raybxqaRu7-B9LjQ8ng@mail.gmail.com>
References: <CAPRqa+GgN6n9nmEUdaP1VxxFddQRwE1QDbxXqT082v3Qy8DzdQ@mail.gmail.com>
	<CAKxcST8D0QscwN2W3KuvOkousqOfB=rBAVUkWJt3BGJ6vCH2Ug@mail.gmail.com>
	<CAPRqa+Ebp+HFJu0nnok4Z=6fvexCyz5pLv5uUc-5syE=a_H6+g@mail.gmail.com>
	<CAKxcST_PckLRmkYUwog=wC4K=Of3tR5cZeYv47e1HZ71C4VBxA@mail.gmail.com>
	<CAPwsocEO3YgWU6dPKa8-g-VQaOqtKmpAH79icVgn4X6w7sVeYQ@mail.gmail.com>
	<CAEZPtU4EK_SE7Q+45Wo=r=Rvt_MFyL9A7ZL35mie8L11-oUgcw@mail.gmail.com>
	<CAKxcST_UgUCMBQt42VZEFwgvPvaaXT3it8YgMytEwKtDX1gDFA@mail.gmail.com>
	<CAEZPtU6YvNBRVX804t4wRBvJpqL7sA6QEsA=8N26c7oOE8EH5A@mail.gmail.com>
	<CAPRqa+HDPNkBmRqeoq2Tp=Eyn=_EZsCK7TSa8Xz1PpKiz3dD1Q@mail.gmail.com>
	<CAPwsocH32Wc0U-xyWDYdCar1rf+bSK3raybxqaRu7-B9LjQ8ng@mail.gmail.com>
Date: Wed, 24 Sep 2014 08:11:47 +0200
Message-ID: <CAEZPtU7TGxSmqZG8+eBCXma_zhD==swMoPmxrxGoFOvHz05tQA@mail.gmail.com>
To: Leigh <leight@gmail.com>
Cc: Park Framework <park.framework@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7b677aaa1fcdbe0503c98f24
Subject: Re: [PHP-DEV] Improve PHP 7 serialization
From: pierre.php@gmail.com (Pierre Joye)

--047d7b677aaa1fcdbe0503c98f24
Content-Type: text/plain; charset=UTF-8

On Sep 23, 2014 8:07 PM, "Leigh" <leight@gmail.com> wrote:
>
> On 23 September 2014 17:36, Park Framework <park.framework@gmail.com>
wrote:
> >
> > If you do not update in PHP 7 serialization method, it will never be
> > updated, the default serialization in PHP 7 will be slow.
> >
> > To maintain backward compatibility, can implement support method calls
> > on primitive types, new algorithms for serialization to be called only
> > in the new API.
> >
> > $var->serialize()
> > $var->unserialize()
> >
> > What do you think about this?
>
> To maintain backward compatibility we leave the behaviour of
> un/serialize() in tact.
>
> There are extensions for alternative serialisation methods and
> regardless of whether any of these becomes a bundled extension, the
> functionality should exist under a different set of function names.

They all exist already. Either for automatic serialization or using
<extname>_(un)serialize, or pack/unpack.

Also as it has been said already, many different extensions exist, each of
them being good in one or many areas. It is like compression methods, use
the right one for the right task.

--047d7b677aaa1fcdbe0503c98f24--