RE: [PEAR-DEV] Re: API's was Benchmarks

> From: Yavor Shahpasov [mailto:yavo@siava.org] > Sent: Thursday, June 05, 2003 4:41 PM > > 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 yes, and following up on this was one of the key decisions at the meeting > 2 DB classes Just a minor note on this: The reason why this is so is because MDB is such a large development effort that it was otherwise not possible to achieve this. > 2 Cache classes I think this, with some minor tweaks, could actually become a rolemodel for the future > Lot's of template classes indeed, gnarf > 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 MDB's API is very very similar to DB's. The changes are what you could expect from a major version jump. Anyways at the meeting we agreed that: - redundant packages are not what we want - merging packages and/or creating "lite" packages which implement only parts of the API are what we want regards, Lukas