Re: Adoption of Metabase
| From: | Peter Bowyer | Date: | Mon, 19 Nov 2001 11:07:44 +0000 |
| Subject: | Re: Adoption of Metabase | ||
| References: | 1 2 3 4 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-2982@lists.php.net to get a copy of this message | ||
Hello,
At 11:09 PM 11/18/01 -0200, you wrote:
OK, let me stick my neck out :-) Metabase was written for PHP3, and therefore if rewritten for PHP4 w Zend Engine 2 would probably see some significant speed increases. Manuel AFAIK Metabase is not affected noticeably in performance due being able to also run with PHP 3.From what I've read, I'm surprised about that, but am willing to be corrected.
already knows my views on the function naming, and I would really like to see it have an API like PEAR-DB - not a wrapper (more overhead) but truly rewritten, to the PEAR standards. Shifting Metabase API to something else would meant droping support to all the existing Metabase applications. The PEAR-DB wrapper was more to keep the PEAR-DB API to please people that are already using PEAR-DB.But we don't want to have an API that in 2 years time we will look back and wish we had changed - by which time there will be many more people using it, and so it cannot be changed. If we changed the API we could always write a Metabase wrapper for it :-)
Now there's an idea: why not port Metabase to C? That is what I was proposing.OK, sorry. I didn't understand your posting. Thanks for the links to projects. Regards, Peter. -- Maple Design - http://www.mapledesign.co.uk