Re: [PHP4BETA] class serialize/unserialize implementation.
| From: | Andrey Zmievski | Date: | Wed, 15 Sep 1999 16:00:18 +0000 |
| Subject: | Re: [PHP4BETA] class serialize/unserialize implementation. | ||
| References: | 1 | Groups: | php.version4 |
| Request: | Send a blank email to php-version4+get-4489@lists.php.net to get a copy of this message | ||
Samuel Liddicott wrote:
> So I'm obviously missing something here. If the benefit of serializing the
> classname with the object is not to help unserialize it, is there some way
> of getting this name out of the serialized class easily in order to pass it
> to unserialize? and if so why can't unserialize just do that?
>
> Or something? Or is there some other reason for serializing the classname?
-- End of excerpt from Samuel Liddicott
Classname by itself is not a description of the object. What Thies was saying
is that you have to have your class defined somewhere before you call
unserialize so that the function can internally create an instance of the
class based on the name it got from the serialized string.
-Andrey
* I don't mind going nowhere as long as it's an interesting path. *