Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:77557
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <5421EB4A.4000101@sugarcrm.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>
	<5421EB4A.4000101@sugarcrm.com>
Date: Wed, 24 Sep 2014 00:56:26 +0300
Message-ID: <CAPRqa+ESx9+N5wHEhrZ-1pPQ-Qa8-RfAidqhRR1k2pw9bwucgA@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: Paul Dragoonis <dragoonis@gmail.com>, Pierre Joye <pierre.php@gmail.com>, Leigh <leight@gmail.com>, 
	PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Improve PHP 7 serialization
From: park.framework@gmail.com (Park Framework)

> Why break anything? If you need faster serializer, it's quite easy to
> get one, including msgpack. If it is really an issue that is important
> for people, we could include the package into core. But I don't see
> breaking BC in serialize/unserialize as a big win here. If it's really a
> bottleneck, a userspace package abstracting the specific serializer
> function could be easily created - and most clients like sessions
> already allow to switch serializers by configs. So BC break does not
> seem to be warranted here.

Perhaps a compromise would be to choose the quickest method of
serialization, add it to PHP core.

In php.ini add the directive
serialization.method = msgpack / Igbinary / ....