Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:18921
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <432872D7.8060606@zend.com>
Date: Wed, 14 Sep 2005 22:58:31 +0400
User-Agent: Thunderbird 1.4 (X11/20050907)
MIME-Version: 1.0
To: Marcus Boerger <helly@php.net>
CC: Andrei Zmievski <andrei@gravitonic.com>, 
	php-dev <internals@lists.php.net>,
	Dmitry Stogov <dmitry@zend.com>
References: <43215A91.8050409@zend.com>	<9CF57DC5-A18B-4264-B20B-8552B0BB66F1@gravitonic.com>	<432194F7.6000703@zend.com> <463148328.20050914160240@marcus-boerger.de>
In-Reply-To: <463148328.20050914160240@marcus-boerger.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] unserialize() & unicode issues
From: antony@zend.com (Antony Dovgal)

On 14.09.2005 18:02, Marcus Boerger wrote:
> Hello Antony,
> 
>   why can't we put a marker there? shouldn't we be able to add a flag
> and allow that flag in older php versions disallowing to load those
> serialized data in case it shows unicode semantics? 

You mean adding a marker to be able to fail with a nice error msg?
I don't think the marker is needed for that (see below).

> Right now we'd
> simply fail in case of unicode usage in any serialized data with old
> php versions. 

Yes. 
And I think it's reasonable as nobody told that the old versions will be forward compatible.

> Adding those types now would at least to show a more
> specific and thus helpful error message. 

I suppose it's better to change 4.4.1/5.0.6/5.1 to fail gracefully when they find an unknown prefix ("U:").

> On te other hand havin the
> semantics flag being optional would allow HEAD to unserialize data
> from older version without any problem.

Didn't get that paragraph... =|
Do we have any problems with serialized data from older versions?
I don't see any of them.

-- 
Wbr, 
Antony Dovgal