Re: API's was Benchmarks
| From: | Yavor Shahpasov | Date: | Thu, 05 Jun 2003 14:41:21 +0000 |
| Subject: | Re: API's was Benchmarks | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-17073@lists.php.net to get a copy of this message | ||
On the matter of API's
Originally it was pear's goal not to allow duplication of package
functionality, unfortunately (or fortunately), this goal failed to some
extent we now have
2 DB classes
2 Cache classes
Lot's of template classes
Now to the point, think there have to be some API's established for more
than DB classes, there are a number of classes which could benefit from this
even without duplication. In existing packages the API can be enforced by
using wrapper methods on existing methods
Here are some groups of pear packages which could benefit from this, example
API's are not really well though of and used just to illustrate the example
POP3/IMAP/other Email Protocol Exchange ???
a common interface for these would be really great
getMessages()
getMessage($num)
deleteMessage($num)
getMessagesNumber()
...
Templates too many to list here :)
assign($var, $value)
parse($tpl)
fetch($tpl)
display($tpl)
...
DB/MDB of cource
query()
getRow($num)
...
Cache/Cache_Lite now these two use a really similar API but there are some
differences
Just My 2c
Yavor
----- Original Message -----
From: "Lukas Smith" <smith@backendmedia.com>
To: "'Björn Schotte'" <bjoern@thinkphphq.de>;
<pear-dev@lists.php.net>
Sent: Thursday, June 05, 2003 4:32 PM
Subject: RE: [PEAR-DEV] Benchmarks
> From: Björn Schotte [mailto:bjoern@thinkphphq.de]
> Sent: Thursday, June 05, 2003 3:23 PM
>
> Hi,
>
> anyone has some recent Benchmarks of PHPLIB's db abstraction layer
> compared to PEAR::DB or PEAR::MDB. I remember PHPLIB::DB was one
> of the fastest. If it's still, I'm interested in porting it to PEAR.
It might be compareably fast indeed. But we should rather examine why
that is so and see if we can improve DB or MDB.
Actually there are a lot of changes looming in the air in how to handle
DB interfacing but in the end I see only two that would have merit to be
in PEAR
1) DB ext API abstraction
2) full DB abstraction (which obviously also includes API abstraction)
Today 1) is done through DB and 2) is done through MDB.
regards,
Lukas
PS: you may also want to take a look at this posting by Tomas:
http://marc.theaimsgroup.com/?l=pear-dev&m=100793507904834&w=2
--
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php