'. '

Category:APIDesignPatterns:Evolution

From APIDesign

Revision as of 12:51, 15 November 2008 by JaroslavTulach (Talk | contribs)
Jump to: navigation, search

First version of an API is never perfect. All the time there is a need to evolve, extend use-cases and provider more functionality. Doing this in backward compatible way ensures that usages of previous version of the API still remains valid and greatly reduces Cost of Ownership and turns the API into good one. The APIDesignPatterns listed in this category are well suited for Evolution:

Personal tools
buy