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

On Fri, 23 Jun 2000, Stanislav Malyshev wrote: > SS>> If the class definition is not available on object > SS>> deserialization, we store the original class name in a hash > SS>> table and assign the object a special class. This class would > SS>> always halt the execution of the script, if any of its > SS>> methods would be called (and output an appropiate text). This > > Where we are going to shove those methods from? And no, I won't stop > repeating this: these fake objects should be hidden from the user. If user > doesn't have class for them, that's a good sign he doesn't want to see > them. So remove them from PHP namespace and store in the internal session > hash. There they won't bother anybody. And you will have no method problem > - there will be nobody to call the methods. Um, the serializer does not have any concept of sessions. What you are suggesting would need a redesign of the session and serializer stuff. - Sascha