Re: persistent PEAR object
| From: | (Stig Sæther Bakken) | Date: | Mon, 21 May 2001 22:17:02 +0000 |
| Subject: | Re: persistent PEAR object | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-427@lists.php.net to get a copy of this message | ||
[Robert Kelly <rkelly@Insight.com>]
> Just curious, has anyone plsyed around with shared memory at all to keep
> persistant DB connections and caching?
I entertained myself with the idea four years ago or so, and came to
the conclusion that doing persistent DB connections with shared memory
and no support from the database library is about as easy and elegant
as moving your car by taking the wheels off and carrying the car.
Most database client libraries have connection structs with file
descriptors and undocumented "magical" blocks of data. You can pass
file desciptors between processes in most operating systems, but it's
not very portable and it sure isn't supported by the database vendors.
IMHO Oracle have done the Right Thing[tm] in Oracle 8 with the
connection dispatcher. Your connection pooling is right there,
independent of the programming language or application.
- Stig
--
Stig Sæther Bakken <ssb@fast.no>
Fast Search & Transfer ASA, Trondheim, Norway