Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115904
MIME-Version: 1.0
References: <20210831155642.1779f22f@mcmic-probook.opensides.be> <20210831161608.1e994d57@mcmic-probook.opensides.be>
In-Reply-To: <20210831161608.1e994d57@mcmic-probook.opensides.be>
Date: Tue, 31 Aug 2021 16:26:30 +0200
Message-ID: <CAF+90c_BygzLBu88qRAKQkdehNUufxWccuD-t24jmJ-YRQuR0w@mail.gmail.com>
To: =?UTF-8?Q?C=C3=B4me_Chilliet?= <come.chilliet@fusiondirectory.org>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000005fbf8e05cadbbd60"
Subject: Re: [PHP-DEV] Resources and object resources
From: nikita.ppv@gmail.com (Nikita Popov)

--0000000000005fbf8e05cadbbd60
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, Aug 31, 2021 at 4:16 PM C=C3=B4me Chilliet <
come.chilliet@fusiondirectory.org> wrote:

> Le Tue, 31 Aug 2021 15:56:42 +0200,
> C=C3=B4me Chilliet <come.chilliet@fusiondirectory.org> a =C3=A9crit :
> > It seems to be consistent accross versions: https://3v4l.org/BHtAh
> >
> > But what will happen when LDAP connections are turned into objects in
> 8.1?
> > Will they also become int(0) upon serialization or will they behave in =
an
> > other way? I could not find a case of resource that became an object an=
d
> is
> > allowed on 3v4l to test this. There is no LDAP or CURL in there.
>
> Quick followup on this, I found a case that can be tested on 3v4l:
> https://3v4l.org/EKFP0
>
> -> Fatal error: Uncaught Exception: Serialization of 'XMLParser' is not
> allowed
> in /in/EKFP0:13
>
> So it seems objects of this kind throw when serialized (I hope they all d=
o
> that).


Unless we made a mistake somewhere, yes, all "resource-like" objects are
not serializable and will throw an attempted serialization or
unserialization.


> It is not clear to me how that behaves with session, will it throw as
> soon as affected to $_SESSION, or at the end of the request?
>

Storing it in $_SESSION temporarily should work fine, it will only throw
when the session is serialized.

Regards,
Nikita

--0000000000005fbf8e05cadbbd60--