Re: [RFC] New custom object serialization mechanism
| From: | naitsirch at e dot mail dot de | Date: | Thu, 24 Jan 2019 13:15:14 +0000 |
| Subject: | Re: [RFC] New custom object serialization mechanism | ||
| Groups: | php.internals | ||
| Request: | Send a blank email to internals+get-103824@lists.php.net to get a copy of this message | ||
On Thu, Jan 24, 2019 at 13:27 Nikita Popov <nikita.ppv@gmail.com>
wrote:
> Hi internals,
>
> I'd like to propose a new custom object serialization mechanism intended to
> replace the broken Serializable interface:
>
> https://wiki.php.net/rfc/custom_object_serialization
>
> This was already previously discussed in
> https://externals.io/message/98834,
> this just brings it into RFC form. The latest motivation for this is
> https://bugs.php.net/bug.php?id=77302, a compatibility issue in
> 7.3
> affecting Symfony, caused by Serializable. We can't fix Serializable, but
> we can at least make sure that a working alternative exists.
>
> Regards,
> Nikita
Hi.
What happens if both
__serialize() and __wakeup() are implemented?
And another idea for the naming: Maybe one could use __normalize() and
__denormalize(). Because the methods do not serialize themself, like the normalizer in
the Symfony serializer component.
Best regards
-------------------------------------------------------------------------------------------------
FreeMail powered by mail.de - MEHR SICHERHEIT, SERIOSITÄT UND KOMFORT