Re: unserialize() & unicode issues
| From: | Antony Dovgal | Date: | Wed, 14 Sep 2005 18:58:31 +0000 |
| Subject: | Re: unserialize() & unicode issues | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-18921@lists.php.net to get a copy of this message | ||
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