Re: persistent PEAR object

The whole idea is to cache the data and not the connection. A good example would be a disconnected record set. Like the once found in .net and borland development platforms "Robert Kelly" <rkelly@Insight.com> wrote in message news:48845550BDD0D211B7580008C7A42DD3274F1163@hqexch1.hq.insight.com... > > Just curious, has anyone plsyed around with shared memory at all to keep > persistant DB connections and caching? > > -B > > -----Original Message----- > From: yavo [mailto:yavo@itena.com.cy] > Sent: Monday, May 21, 2001 5:29 AM > To: pear-dev@lists.php.net > Subject: [PEAR-DEV] persistent PEAR object > > > A common problem with web pages is that they do not preserve any data among > requests. I had the following idea last night. use a combination of > Cache/phpsessionid/Pear constructors destructors to preserve the state of > objects. > > Here is how it would work. > *) when constructor is called it chechs it a combination of > phpseshid_objectname is found in the cache (you'll need some additional info > to generate the UID, or maybe save diffrent object types in diffrent cache > repositories) if found load it in the current object. > **) when destructor is called, save the object in the cache. > > Benefits > reduse load on the database (if one) > object persistance, you don't have to save/load data beetwin requests (you > do but it's done internally) > easier to build distrubuted applications (if using a common repository for > multiple servers) > > Comments ??? > > yavo > > > > > > -- > PEAR Development Mailing List (http://pear.php.net/) > To unsubscribe, e-mail: pear-dev-unsubscribe@lists.php.net > For additional commands, e-mail: pear-dev-help@lists.php.net > To contact the list administrators, e-mail: php-list-admin@lists.php.net >