Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:27562
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain widescreen.ch from 62.2.95.247 cause and error)
Message-ID: <45B39184.7010904@widescreen.ch>
Date: Sun, 21 Jan 2007 17:15:00 +0100
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
MIME-Version: 1.0
To: internals@lists.php.net
References: <45B0E1EE.2030102@widescreen.ch> <200701192122.38663.pstradomski@gmail.com>
In-Reply-To: <200701192122.38663.pstradomski@gmail.com>
Content-Type: text/plain; charset=ISO-8859-2; format=flowed
Content-Transfer-Encoding: 7bit
X-DCC-spamcheck-02.tornado.cablecom.ch-Metrics: smtp-06.tornado.cablecom.ch 1378;
	Body=1 Fuz1=1 Fuz2=1
Subject: Re: [PHP-DEV] PHP Object-Caching and Reference Counting
From: schultz@widescreen.ch (Lars Schultz)


>Perhaps you could use your own reference counting?
>Keep your "real" objects in private array and instead of returning them return 
>a simple object which would forward all methods and properties by 
>__get/__set/__call. The constructor would increase your internal refcount by 
>one, destructor would decrease it.
>  
>
I use those objects quite often as they are used to access the database 
to manipulate or search for related data. It wouldn't perform well and 
is actually not at all practicable because there are so many classes for 
which I'd would have to copy the interface.