Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:15513 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 98567 invoked by uid 1010); 20 Mar 2005 20:18:42 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 98552 invoked from network); 20 Mar 2005 20:18:42 -0000 Received: from unknown (HELO marcus-boerger.de) (127.0.0.1) by localhost with SMTP; 20 Mar 2005 20:18:42 -0000 X-Host-Fingerprint: 81.169.182.136 h59705.serverkompetenz.net Linux 2.4/2.6 Received: from ([81.169.182.136:56980] helo=strato.aixcept.de) by pb1.pair.com (ecelerity HEAD r(5268)) with SMTP id 0A/93-17247-1AADD324 for ; Sun, 20 Mar 2005 15:18:42 -0500 Received: from [192.168.1.3] (dsl-082-083-254-021.arcor-ip.net [82.83.254.21]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by strato.aixcept.de (Postfix) with ESMTP id 8DF5835C1D0; Sun, 20 Mar 2005 21:23:02 +0100 (CET) Date: Sun, 20 Mar 2005 21:18:42 +0100 Reply-To: Marcus Boerger X-Priority: 3 (Normal) Message-ID: <545016232.20050320211842@marcus-boerger.de> To: l0t3k Cc: internals@lists.php.net, l0t3k In-Reply-To: <20050320201124.87674.qmail@lists.php.net> References: <20050320012716.26297.qmail@lists.php.net> <1245669636.20050320203441@marcus-boerger.de> <20050320201124.87674.qmail@lists.php.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Serialization question From: mail@marcus-boerger.de (Marcus Boerger) Hello l0t3k, Monday, March 21, 2005, 12:14:03 PM, you wrote: > Marcus, > i just read through var.c (specifically php_var_serialize_intern) and it > seems as if the properties hash is handled correctly if the user specifies > __sleep and __wakeup. > IOW, the custom callback is called, then _sleep is called to determine how > to further handle properties. Thanks for checking that, i didn't new and imho it is absolutley wrong. Instead the user should call that funcs his own in an overloaded class of the c code should enforce calling it otherwise. I think so becuase the whole idea of being able to overload serializing at c level is that there might be classes that do not have standard properties implemented and hence a call to __sleep/__wakeup does not make sense. regards marcus > "Marcus Boerger" wrote in message > news:1245669636.20050320203441@marcus-boerger.de... >> You have to do all your own (.) answers all further question >> >> (snip) >> >> marcus -- Best regards, Marcus mailto:mail@marcus-boerger.de