Evolution

From APIDesign

(Difference between revisions)
Jump to: navigation, search
Line 1: Line 1:
-
Evolution of an [[API]] requires well though plan. When designed an [[API]] get ready for it being insufficient and imagine potential direction of future changes. Design the [[API]] to allow such changes to be done in [[BackwardCompatibility|backward compatible]] way. Use proper [[Category:APIDesignPatterns:Evolution|API Design patterns]] to make your future job easier.
+
Evolution of an [[API]] requires well though plan. When designed an [[API]] get ready for it being insufficient and imagine potential direction of future changes. Design the [[API]] to allow such changes to be done in [[BackwardCompatibility|backward compatible]] way. Use proper [[APIDesignPatterns|API Design patterns]] to make your future job easier.

Revision as of 12:50, 15 November 2008

Evolution of an API requires well though plan. When designed an API get ready for it being insufficient and imagine potential direction of future changes. Design the API to allow such changes to be done in backward compatible way. Use proper API Design patterns to make your future job easier.

Personal tools
buy