Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:19742
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 26 Oct 2005 23:19:29 +0200
Message-ID: <00A2E2156BEE8446A81C8881AE117F192C1866@companyweb>
Thread-Topic: [PHP-DEV] Questions about "static" and serialization
Thread-Index: AcXaLuCxExeYkz27SfqWgWDPKFjnWAARAzLg
To: <internals@lists.php.net>
Subject: AW: [PHP-DEV] Questions about "static" and serialization
From: mp@webfactory.de ("Matthias Pigulla")

> Von: Wez Furlong [mailto:kingwez@gmail.com]=20
>=20
> As you mentioned, static properties and statically scoped=20
> variables don't belong to an object instance, so it doesn't=20
> make sense to serialize them.

Ok, but on the other hand they are just variables - so the question was
if there is any (possibly userland) way to capture them in the line with
"normal" session handling, by using (un)serialize or whatever.

As to persisting and restoring structures like the singleton pattern, I
just noticed that the builtin serialization/persistence mechanisms don't
care about object identity at all... :(

Best regards,
Matthias