Evolution - Revision history

JaroslavTulach: Redirecting to Category:APIDesignPatterns:Evolution

JaroslavTulach — Wed, 29 Sep 2010 21:10:08 GMT

Redirecting to Category:APIDesignPatterns:Evolution

←Older revision		Revision as of 21:10, 29 September 2010
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 [[APIDesignPatterns~~\|API Design patterns~~]] ~~to make your future job easier.~~	+	#REDIRECT [[:Category:APIDesignPatterns:Evolution]]

JaroslavTulach at 12:50, 15 November 2008

JaroslavTulach — Sat, 15 Nov 2008 12:50:13 GMT

←Older revision		Revision as of 12:50, 15 November 2008
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.

JaroslavTulach at 12:49, 15 November 2008

JaroslavTulach — Sat, 15 Nov 2008 12:49:35 GMT

←Older revision		Revision as of 12:49, 15 November 2008
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 [[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 [[Category:APIDesignPatterns:Evolution\|API Design patterns]] to make your future job easier.

JaroslavTulach: New page: 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 all...

JaroslavTulach — Sat, 15 Nov 2008 12:49:17 GMT

New page: 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 all...

New page

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:Evolution|API Design patterns]] to make your future job easier.