Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:42469
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain schlueters.de from 83.243.58.133 cause and error)
To: Marcin Kurzyna <m.kurzyna@crystalpoint.pl>
Cc: internals@lists.php.net, Marcus Boerger <helly@php.net>
In-Reply-To: <495F6457.6060201@crystalpoint.pl>
References: <87.E1.28540.1817E594@pb1.pair.com>
	 <1811359335.20090102211222@marcus-boerger.de>
	 <495F6457.6060201@crystalpoint.pl>
Content-Type: text/plain
Date: Sun, 04 Jan 2009 14:35:39 +0100
Message-ID: <1231076139.6023.9.camel@goldfinger>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Closures serialization
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

On Sat, 2009-01-03 at 14:12 +0100, Marcin Kurzyna wrote:
> as you said it's saving the zend_function member that is tricky. i 
> thought i'd go with saving function string and recompiling it as you 
> suggested (i don't want to mess with APC although i find the idea of 
> opcode serialization much more appealing). anyway it's proving itself, 
> well... tricky ;-)

Two thoughts:

- It can be quite tricky to keep the binding of "use"d variables correct

- Serialized data soften used as data exchange format (for instance
<http://developer.yahoo.com/common/phpserial.html>) the default
unserialize shouldn't introduce executable code even though it's not
executed by default we should be careful there. And yes, I can
understand the need to serialize object structures, including closures,
to sessions...

johannes