Evolving the API Universe - Revision history

JaroslavTulach: /* Have You Ever Wondered...? */

JaroslavTulach — Fri, 26 Jun 2009 09:20:22 GMT

Have You Ever Wondered...?

←Older revision		Revision as of 09:20, 26 June 2009
Line 4:		Line 4:

	This [[Evolving the API Universe\|chapter]] also shortly mentions [[Singletonizer]], an interesting creational [[APIDesignPatterns\|API design pattern]]. However more information is available [[Singletonizer\|online]].		This [[Evolving the API Universe\|chapter]] also shortly mentions [[Singletonizer]], an interesting creational [[APIDesignPatterns\|API design pattern]]. However more information is available [[Singletonizer\|online]].
		+
		+	Section ''Resuscitating Broken Libraries'' also introduces testing style to guarantee full [[BackwardCompatibility]] when rewriting implementation behind existing [[API]] - the [[ImplementationCompatibilityTest]].

JaroslavTulach: /* Have You Ever Wondered...? */

JaroslavTulach — Mon, 16 Feb 2009 16:31:54 GMT

Have You Ever Wondered...?

←Older revision		Revision as of 16:31, 16 February 2009
Line 1:		Line 1:
	== [[Have You Ever Wondered]]...? ==		== [[Have You Ever Wondered]]...? ==

-	Have you ever were afraid to release your API because you knew the implementation behind it is not good enough? Have you been afraid of the API's future? Of numerous bugs, each creating another incompatibility? [[Evolving the API Universe\|Chapter 15]] explains that you do not have to! If you design your API to be ready for evolution, you can resuscitate even bad design of your broken libraries without doing incompatible changes. All that is needed is to know the right way of introducing alternative behaviours and also knowing how to allow coexistence of similar APIs.	+	Have you ever were afraid to release your API because you knew the implementation behind it is not good enough? Have you been afraid of the API's future? Of numerous bugs, each creating another incompatibility? [[Evolving the API Universe\|Chapter 15]] explains that you do not have to! If you design your API to be ready for evolution, you can resuscitate even bad design of your broken libraries without doing incompatible changes. All that is needed is to know the right way of introducing [[AlternativeBehaviour\|alternative behaviours]] and also knowing how to allow coexistence of similar APIs.

	This [[Evolving the API Universe\|chapter]] also shortly mentions [[Singletonizer]], an interesting creational [[APIDesignPatterns\|API design pattern]]. However more information is available [[Singletonizer\|online]].		This [[Evolving the API Universe\|chapter]] also shortly mentions [[Singletonizer]], an interesting creational [[APIDesignPatterns\|API design pattern]]. However more information is available [[Singletonizer\|online]].

JaroslavTulach: /* Have You Ever Wondered...? */

JaroslavTulach — Tue, 30 Dec 2008 12:44:26 GMT

Have You Ever Wondered...?

←Older revision		Revision as of 12:44, 30 December 2008
Line 3:		Line 3:
	Have you ever were afraid to release your API because you knew the implementation behind it is not good enough? Have you been afraid of the API's future? Of numerous bugs, each creating another incompatibility? [[Evolving the API Universe\|Chapter 15]] explains that you do not have to! If you design your API to be ready for evolution, you can resuscitate even bad design of your broken libraries without doing incompatible changes. All that is needed is to know the right way of introducing alternative behaviours and also knowing how to allow coexistence of similar APIs.		Have you ever were afraid to release your API because you knew the implementation behind it is not good enough? Have you been afraid of the API's future? Of numerous bugs, each creating another incompatibility? [[Evolving the API Universe\|Chapter 15]] explains that you do not have to! If you design your API to be ready for evolution, you can resuscitate even bad design of your broken libraries without doing incompatible changes. All that is needed is to know the right way of introducing alternative behaviours and also knowing how to allow coexistence of similar APIs.

-	This [[Evolving the API Universe\|chapter]] also shortly mentions [[Singletonizer]], an interesting creational [[~~APIDesignPattern~~\|API design pattern]]. However more information is available [[Singletonizer\|online]].	+	This [[Evolving the API Universe\|chapter]] also shortly mentions [[Singletonizer]], an interesting creational [[APIDesignPatterns\|API design pattern]]. However more information is available [[Singletonizer\|online]].

JaroslavTulach at 12:44, 30 December 2008

JaroslavTulach — Tue, 30 Dec 2008 12:44:05 GMT

←Older revision		Revision as of 12:44, 30 December 2008
Line 2:		Line 2:

	Have you ever were afraid to release your API because you knew the implementation behind it is not good enough? Have you been afraid of the API's future? Of numerous bugs, each creating another incompatibility? [[Evolving the API Universe\|Chapter 15]] explains that you do not have to! If you design your API to be ready for evolution, you can resuscitate even bad design of your broken libraries without doing incompatible changes. All that is needed is to know the right way of introducing alternative behaviours and also knowing how to allow coexistence of similar APIs.		Have you ever were afraid to release your API because you knew the implementation behind it is not good enough? Have you been afraid of the API's future? Of numerous bugs, each creating another incompatibility? [[Evolving the API Universe\|Chapter 15]] explains that you do not have to! If you design your API to be ready for evolution, you can resuscitate even bad design of your broken libraries without doing incompatible changes. All that is needed is to know the right way of introducing alternative behaviours and also knowing how to allow coexistence of similar APIs.
		+
		+	This [[Evolving the API Universe\|chapter]] also shortly mentions [[Singletonizer]], an interesting creational [[APIDesignPattern\|API design pattern]]. However more information is available [[Singletonizer\|online]].

JaroslavTulach: /* Have You Ever Wondered...? */

JaroslavTulach — Tue, 26 Aug 2008 19:07:17 GMT

Have You Ever Wondered...?

←Older revision		Revision as of 19:07, 26 August 2008
Line 1:		Line 1:
	== [[Have You Ever Wondered]]...? ==		== [[Have You Ever Wondered]]...? ==

-	Have you ever were afraid to release your API because you knew the implementation behind it is not good enough? Have you been afraid of the API's future? Of numerous bugs, each creating another incompatibility? [[Evolving the API Universe\|Chapter 15] explains that you do not have to! If you design your API to be ready for evolution, you can resuscitate even bad design of your broken libraries without doing incompatible changes. All that is needed is to know the right way of introducing alternative behaviours and also knowing how to allow coexistence of similar APIs.	+	Have you ever were afraid to release your API because you knew the implementation behind it is not good enough? Have you been afraid of the API's future? Of numerous bugs, each creating another incompatibility? [[Evolving the API Universe\|Chapter 15]] explains that you do not have to! If you design your API to be ready for evolution, you can resuscitate even bad design of your broken libraries without doing incompatible changes. All that is needed is to know the right way of introducing alternative behaviours and also knowing how to allow coexistence of similar APIs.

JaroslavTulach: /* Have You Ever Wondered...? */

JaroslavTulach — Tue, 26 Aug 2008 19:01:26 GMT

Have You Ever Wondered...?

←Older revision		Revision as of 19:01, 26 August 2008
Line 1:		Line 1:
	== [[Have You Ever Wondered]]...? ==		== [[Have You Ever Wondered]]...? ==

-	Have you ever were afraid to release your API because you knew the implementation behind it is not good enough? Have you been afraid of the API's future? Of numerous bugs, each creating another incompatibility? [[Evolving the API Universe\|Chapter 15] explains that you do not have to! If you design your API to be ready for evolution, you can resuscitate even bad design of your broken libraries without doing incompatible changes.	+	Have you ever were afraid to release your API because you knew the implementation behind it is not good enough? Have you been afraid of the API's future? Of numerous bugs, each creating another incompatibility? [[Evolving the API Universe\|Chapter 15] explains that you do not have to! If you design your API to be ready for evolution, you can resuscitate even bad design of your broken libraries without doing incompatible changes. All that is needed is to know the right way of introducing alternative behaviours and also knowing how to allow coexistence of similar APIs.

JaroslavTulach at 19:54, 17 August 2008

JaroslavTulach — Sun, 17 Aug 2008 19:54:09 GMT

←Older revision		Revision as of 19:54, 17 August 2008
Line 1:		Line 1:
-	~~Designing~~ is ~~done once a time~~, the ~~real work in to maintain what we~~ have ~~designed previously~~.	+	== [[Have You Ever Wondered]]...? ==
		+
		+	Have you ever were afraid to release your API because you knew the implementation behind it is not good enough? Have you been afraid of the API's future? Of numerous bugs, each creating another incompatibility? [[Evolving the API Universe\|Chapter 15] explains that you do not have to! If you design your API to be ready for evolution, you can resuscitate even bad design of your broken libraries without doing incompatible changes.

Apidesign: New page: Designing is done once a time, the real work in to maintain what we have designed previously.

Apidesign — Sat, 14 Jun 2008 06:23:49 GMT

New page: Designing is done once a time, the real work in to maintain what we have designed previously.

New page

Designing is done once a time, the real work in to maintain what we have designed previously.