Re: PHPLib -> PEAR

I posed this question in the last mail, but it is important enough to warrant a separate mail: How mature is the PHPLIB db abstraction layer? is it being used in any large, clustered webserver installations? What databases does it support? I'm trying to form a coherent plan that will allow both PEAR and binarycloud to grow without tangling in each other's roots. The only problems I'm seeing are the use (and thus dependence upon) of a customer PEAR error handler, and the PEAR::DB stuff. everything else is just libraries, and binarycloud eats libraries like candy :) _alex -- Alex Black, Head Monkey enigma@turingstudio.com The Turing Studio, Inc. http://www.turingstudio.com vox+510.666.0074 fax+510.666.0093 Saul Zaentz Film Center 2600 Tenth St Suite 433 Berkeley, CA 94710-2522 > From: sb@sebastian-bergmann.de (Sebastian Bergmann) > Organization: http://www.sebastian-bergmann.de/ > Newsgroups: php.pear > Date: 17 Jan 2001 21:34:04 -0800 > Subject: Re: [PHP-PEAR] PHPLib -> PEAR > > André Langhorst wrote: >> afaik, PHPLib carries an own db layer, is it supposed to stay or >> merged/adopted with PEAR db classes? > > True, everything related to databases in PHPLIB builds upon PHPLIB's > database abstraction layer. We'll have to port all that to PEAR::DB. > > -- > sebastian bergmann e-mail : sb@sebastian-bergmann.de > homepage : http://www.sebastian-bergmann.de > make a gift : http://wishlist.sebastian-bergmann.de > measure the usability of your web application -> > http://phpOpenTracker.de > > -- > PHP Extension and Add-on Repository (PEAR) mailing list. > Documentation can be found at http://pear.php.net/doc/pear.html > To unsubscribe, e-mail: php-pear-unsubscribe@lists.php.net from the > mail address you subscribed with. >