Re: PHP 4.0 Bug #5152: Object passed in a session generates errors when member functions are called

SS>> We agree on: SS>> SS>> - PHP needs to preserve the name of the class of a SS>> serialized object, even if the class definition is not SS>> available during deserialization. Well, if it'd be possible not to show object too, that would be even better (what you want from the object if you even don't know it's class?). Another thing is to define some dummy class name (like "\0Foo") for that object, and then when storing it back revert to an old class name. I think combining this two solutions (with a warning or notice) would achieve maximum sum of happiness among users. That would complicate session data a bit, but I don't think too much (one additional hash of hidden objects). -- Stanislav Malyshev stas@zend.com +972-3-6139665