Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:23052
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
	s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=pdpRoN/9nmOWrAdAwLCJGQP0TOkRvikLLK+47CXDlw751dZ+uDPwtBLf0U/u5aVHklAKSJtcrmWBxGyXb6W2Q2yGKdq0e6cJ02UgS37Qjw5V3nQTkJBBREp6mBfRYVcSsdA9PamZErhVqqJ6GJ0q8sQIQJMC9Skm2tvtfXUoQAM=
Message-ID: <4e89b4260604300631j6f855a59wc008cc320ff8f48f@mail.gmail.com>
Date: Sun, 30 Apr 2006 09:31:15 -0400
To: "Brandon Fosdick" <bfoz@bfoz.net>
Cc: internals@lists.php.net
In-Reply-To: <445447FB.5060306@bfoz.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <445447FB.5060306@bfoz.net>
Subject: Re: [PHP-DEV] resources vs objects?
From: kingwez@gmail.com ("Wez Furlong")

Resources are the traditional approach for mapping an arbitrary
pointer to PHP space, managing its lifetime safely.

PHP 5 OO support allows for similar things, but maps the pointer as a
PHP object.

They're similar in some ways, but different in others.  The biggest
functional difference (aside from OO) is that you can't create
persistent objects (ala mysql_pconnect())--you have to use resources
for that.

It's usually faster to write a procedural extension using resources
than it is to write an OO extension using PHP 5 objects, although the
latter can be more accessible to the consumers of your extension.

Resources:  work with PHP 4.  Can be persistent.
Objects:      work with PHP 5 and up.

There is no hard and fast rule about which one you choose; just use
the one the makes most sense for the task at hand.

--Wez.

On 4/30/06, Brandon Fosdick <bfoz@bfoz.net> wrote:
> From the point of view of an extension, what's the difference between a r=
esource and an object? Is there any reason to favor one over the other?
>
> sqlite seems to use resources for the procedural interface and objects ot=
herwise. Whereas mysqli uses objects all around in user space, but then map=
s them to resources in the background. Why use objects only to map them to =
resources? Are resources somehow special?
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>