Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103834
MIME-Version: 1.0
References: <20190124131514.CD9051000DB@smtp02.mail.de> <CAF+90c8O4DttLY3G=0H8d2fxizDcp61Xud4y2niJRgFPFqPc4g@mail.gmail.com>
 <CAOWwgpnY=DRRBHiOJX_CEKwxAb1wuTnOCfjy95B4emGbtqfQQw@mail.gmail.com>
 <96949d28-1b59-4d8b-9db7-6c5047d180f7@www.fastmail.com> <CAF+90c-v-Y+oj_oVxOu2QRq89TxpqcF3EtOkTdy7DaV89As7Rg@mail.gmail.com>
 <20190124145342.305136480532@dd16914.kasserver.com>
In-Reply-To: <20190124145342.305136480532@dd16914.kasserver.com>
Date: Thu, 24 Jan 2019 15:00:07 +0000
Message-ID: <CALKiJKpUKWut3Q07ZSwg+=sPcvD9VEcdWe8Vt-ZKuGwqxUdQjA@mail.gmail.com>
To: Thomas Bley <mails@thomasbley.de>
Cc: Nikita Popov <nikita.ppv@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000ff24aa058035776b"
Subject: Re: [PHP-DEV] [RFC] New custom object serialization mechanism
From: rowan.collins@gmail.com (Rowan Collins)

--000000000000ff24aa058035776b
Content-Type: text/plain; charset="UTF-8"

On Thu, 24 Jan 2019 at 14:53, Thomas Bley <mails@thomasbley.de> wrote:

> To me it's not clear why we need all these methods, for example:
>
> $a = new A();
> $aSerialized = serialize($a->toArray());
> $aRestored = A::createFromArray(unserialize($aSerialized));
>
> Apart from security problems, problems with versioning and unreadable data
> in databases,
> I don't see many benefits from using serialize()/unserialize().
>


That looks like basically the same methods as proposed, but with different
names: class A has implemented toArray(), and it either recursively calling
toArray() on other objects, or is returning those instances for default
handling by serialize().

If the proposed functions were marked as a generic serialization interface,
as Larry suggests, they would just be standardising this exact pattern.

Regards,
-- 
Rowan Collins
[IMSoP]

--000000000000ff24aa058035776b--