Re: unserialize() & unicode issues
| From: | Andrei Zmievski | Date: | Fri, 09 Sep 2005 14:09:50 +0000 |
| Subject: | Re: unserialize() & unicode issues | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-18745@lists.php.net to get a copy of this message | ||
The problems you encountered are fairly big, I wouldn't just dismiss them.
-Andrei
On Sep 9, 2005, at 6:58 AM, Antony Dovgal wrote:
On 09.09.2005 17:44, Andrei Zmievski wrote:Yes, serialization is a problem. I would actually advocate putting a marker in the serialized file that indicates what the value of unicode_semantics switch was during the serialization, and if the value is different during deserialization, refuse to load it or start a new session. One really should not be changing that switch on a whim in-between sessions.Why? It loads/works perfectly fine except for the problems I've mentioned. Also, you can't put any markers to the serialized _text_ (at least it sounds very bad to me), so it won't help you in this case. --Wbr, Antony Dovgal