Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:27565
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 66.249.92.170 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:from:reply-to:to:subject:date:user-agent:references:in-reply-to:mime-version:content-disposition:message-id:content-type:content-transfer-encoding;
        b=ZLaPHE4JKhyLsIVEZsXNqipfyrVKIuGO535PXtVzwvqblSMKRsozQ/7pDJnTQZIhbDoQJ5zdet0cIp5b9TpnsFHbIxlqukcxHgoKGT4kfgKU+pr/yu8mUf9kuc+1Jl3Tq6ZVw5vU+x7oULKutOFD9kqQ6wGe3zMhZ+Fz/9Zi218=
Reply-To: =?iso-8859-2?q?Pawe=B3_Stradomski?= <pstradomski@gmail.com>
To: internals@lists.php.net
Date: Sun, 21 Jan 2007 17:33:41 +0100
User-Agent: KMail/1.9.5
References: <45B0E1EE.2030102@widescreen.ch> <200701192122.38663.pstradomski@gmail.com> <45B39184.7010904@widescreen.ch>
In-Reply-To: <45B39184.7010904@widescreen.ch>
MIME-Version: 1.0
Content-Disposition: inline
Message-ID: <200701211733.41473.pstradomski@gmail.com>
Content-Type: text/plain;
  charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] PHP Object-Caching and Reference Counting
From: pstradomski@gmail.com (=?iso-8859-2?q?Pawe=B3_Stradomski?=)

On 21 jan 2007 Lars Schultz wrote:
> >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 refcou=
nt
> > 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.

I don't see any place where you'd have to change the interface - except for=
=20
the class which contains that private array; you can use the name of your=20
current  class (MyObject)as the name of this new "forwarding" class and mak=
e a=20
new name for the class which would be a copy of your current class (eg.=20
MyObject_private). Therefore in all function definitions required class=20
specification doesn't need to change.

Well, perhaps you would have to change some "factory" class if you use one,=
=20
but that should be a one place - if you kept your code clean.


I think this solution is better, as you don't have to rely on internal=20
refcounts, which can be implemented in another way (or dropped altogether) =
in=20
future releases.

=2D-=20
Pawe=B3 Stradomski