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? Right now we'd simply fail in case of unicode usage in any serialized data with old php versions. Adding those types now would at least to show a more specific and thus helpful error message. On te other hand havin the semantics flag being optional would allow HEAD to unserialize data from older version without any problem.
regards marcus Friday, September 9, 2005, 3:58:15 PM, you 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. Best regards, Marcus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
