RE: [PHP4BETA] class serialize/unserialize implementation.
| From: | Samuel Liddicott | Date: | Wed, 15 Sep 1999 15:55:43 +0000 |
| Subject: | RE: [PHP4BETA] class serialize/unserialize implementation. | ||
| References: | 1 | Groups: | php.version4 |
| Request: | Send a blank email to php-version4+get-4488@lists.php.net to get a copy of this message | ||
> -----Original Message-----
> From: Andrey Zmievski [mailto:zmievski@ispi.net]
> Sent: Wednesday, September 15, 1999 04:18 PM
> To: Samuel Liddicott; Thies C. Arntzen
> Cc: php4beta@lists.php.net
> Subject: Re: [PHP4BETA] class serialize/unserialize implementation.
>
>
> Samuel Liddicott wrote:
> > So whats the benefit of the recent change to store the classname when
> > serialized?
>
> Because you need to know the name of the class to instance it.
Thies just said:
> the script *has* to have the class availavle *BEFORE* using unserialize -
> elsewise unserialize will simply ignore the object.
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?
Sam