Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:10056
Return-Path: <jason@ionzoft.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 81861 invoked by uid 1010); 23 May 2004 21:48:47 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 81837 invoked from network); 23 May 2004 21:48:47 -0000
Received: from unknown (HELO theta.altoona-pa.com) (209.161.72.28)
  by pb1.pair.com with SMTP; 23 May 2004 21:48:47 -0000
Received: from ionzoft-jeg.ionzoft.com (dpvc-207-68-114-163.alt.east.verizon.net [207.68.114.163])
	by theta.altoona-pa.com (Postfix) with ESMTP id 0049A14AF2
	for <internals@lists.php.net>; Sun, 23 May 2004 17:48:47 -0400 (EDT)
Message-ID: <5.1.0.14.0.20040523174015.02197460@mail.ionzoft.com>
X-Sender: izftjason@mail.ionzoft.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Sun, 23 May 2004 17:48:57 -0400
To: internals@lists.php.net
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: Destructors
From: jason@ionzoft.com (Jason Garber)

Hello,

This is a question relating to the new PHP5 Object Destructor 
functionality.  Consider the following:

<?php

class DB
{
    function Query() { ... }
}

class Session
{
    function SetVar() {
       //sets a variable to be saved in the session
    }

    function __destruct() {
       //Save session variables in database using global $oDB object.
       global $oDB;
       $oDB->Query(...);
    }
}

$oDB = new DB();

$oSession = new Session();
$oSession->SetVar('foo', 'New Value');

//End of script
?>


Based on the above example, the $oSession->__destruct() method relies on 
the $oDB object still being usable.  How can this be structured to ensure 
that the DB object does not get released first?

Thanks,
Jason



__________________________________________________________
Jason Garber
President & Chief Technology Officer
IonZoft, Inc.
814.742.8030 :: jason@ionzoft.com :: http://IonZoft.com
__________________________________________________________