http://wiki.apidesign.org/index.php?title=Evolving_the_API_Universe&feed=atom&action=historyEvolving the API Universe - Revision history2024-03-28T11:20:50ZRevision history for this page on the wikiMediaWiki 1.12.0rc1http://wiki.apidesign.org/index.php?title=Evolving_the_API_Universe&diff=2595&oldid=prevJaroslavTulach: /* Have You Ever Wondered...? */2009-06-26T09:20:22Z<p><span class="autocomment">Have You Ever Wondered...?</span></p>
<table style="background-color: white; color:black;">
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr>
<td colspan='2' style="background-color: white; color:black;">←Older revision</td>
<td colspan='2' style="background-color: white; color:black;">Revision as of 09:20, 26 June 2009</td>
</tr>
<tr><td colspan="2" class="diff-lineno">Line 4:</td>
<td colspan="2" class="diff-lineno">Line 4:</td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>This [[Evolving the API Universe|chapter]] also shortly mentions [[Singletonizer]], an interesting creational [[APIDesignPatterns|API design pattern]]. However more information is available [[Singletonizer|online]].</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>This [[Evolving the API Universe|chapter]] also shortly mentions [[Singletonizer]], an interesting creational [[APIDesignPatterns|API design pattern]]. However more information is available [[Singletonizer|online]].</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;"></ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;">Section ''Resuscitating Broken Libraries'' also introduces testing style to guarantee full [[BackwardCompatibility]] when rewriting implementation behind existing [[API]] - the [[ImplementationCompatibilityTest]].</ins></div></td></tr>
</table>JaroslavTulachhttp://wiki.apidesign.org/index.php?title=Evolving_the_API_Universe&diff=2051&oldid=prevJaroslavTulach: /* Have You Ever Wondered...? */2009-02-16T16:31:54Z<p><span class="autocomment">Have You Ever Wondered...?</span></p>
<table style="background-color: white; color:black;">
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr>
<td colspan='2' style="background-color: white; color:black;">←Older revision</td>
<td colspan='2' style="background-color: white; color:black;">Revision as of 16:31, 16 February 2009</td>
</tr>
<tr><td colspan="2" class="diff-lineno">Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>== [[Have You Ever Wondered]]...? ==</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>== [[Have You Ever Wondered]]...? ==</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr>
<tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div>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.</div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>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 <ins style="color: red; font-weight: bold; text-decoration: none;">[[AlternativeBehaviour|</ins>alternative behaviours<ins style="color: red; font-weight: bold; text-decoration: none;">]] </ins>and also knowing how to allow coexistence of similar APIs.</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>This [[Evolving the API Universe|chapter]] also shortly mentions [[Singletonizer]], an interesting creational [[APIDesignPatterns|API design pattern]]. However more information is available [[Singletonizer|online]].</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>This [[Evolving the API Universe|chapter]] also shortly mentions [[Singletonizer]], an interesting creational [[APIDesignPatterns|API design pattern]]. However more information is available [[Singletonizer|online]].</div></td></tr>
</table>JaroslavTulachhttp://wiki.apidesign.org/index.php?title=Evolving_the_API_Universe&diff=1824&oldid=prevJaroslavTulach: /* Have You Ever Wondered...? */2008-12-30T12:44:26Z<p><span class="autocomment">Have You Ever Wondered...?</span></p>
<table style="background-color: white; color:black;">
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr>
<td colspan='2' style="background-color: white; color:black;">←Older revision</td>
<td colspan='2' style="background-color: white; color:black;">Revision as of 12:44, 30 December 2008</td>
</tr>
<tr><td colspan="2" class="diff-lineno">Line 3:</td>
<td colspan="2" class="diff-lineno">Line 3:</td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>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.</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>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.</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr>
<tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div>This [[Evolving the API Universe|chapter]] also shortly mentions [[Singletonizer]], an interesting creational [[<del style="color: red; font-weight: bold; text-decoration: none;">APIDesignPattern</del>|API design pattern]]. However more information is available [[Singletonizer|online]].</div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>This [[Evolving the API Universe|chapter]] also shortly mentions [[Singletonizer]], an interesting creational [[<ins style="color: red; font-weight: bold; text-decoration: none;">APIDesignPatterns</ins>|API design pattern]]. However more information is available [[Singletonizer|online]].</div></td></tr>
</table>JaroslavTulachhttp://wiki.apidesign.org/index.php?title=Evolving_the_API_Universe&diff=1823&oldid=prevJaroslavTulach at 12:44, 30 December 20082008-12-30T12:44:05Z<p></p>
<table style="background-color: white; color:black;">
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr>
<td colspan='2' style="background-color: white; color:black;">←Older revision</td>
<td colspan='2' style="background-color: white; color:black;">Revision as of 12:44, 30 December 2008</td>
</tr>
<tr><td colspan="2" class="diff-lineno">Line 2:</td>
<td colspan="2" class="diff-lineno">Line 2:</td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>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.</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>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.</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;"></ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;">This [[Evolving the API Universe|chapter]] also shortly mentions [[Singletonizer]], an interesting creational [[APIDesignPattern|API design pattern]]. However more information is available [[Singletonizer|online]].</ins></div></td></tr>
</table>JaroslavTulachhttp://wiki.apidesign.org/index.php?title=Evolving_the_API_Universe&diff=1309&oldid=prevJaroslavTulach: /* Have You Ever Wondered...? */2008-08-26T19:07:17Z<p><span class="autocomment">Have You Ever Wondered...?</span></p>
<table style="background-color: white; color:black;">
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr>
<td colspan='2' style="background-color: white; color:black;">←Older revision</td>
<td colspan='2' style="background-color: white; color:black;">Revision as of 19:07, 26 August 2008</td>
</tr>
<tr><td colspan="2" class="diff-lineno">Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>== [[Have You Ever Wondered]]...? ==</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>== [[Have You Ever Wondered]]...? ==</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr>
<tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div>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.</div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>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<ins style="color: red; font-weight: bold; text-decoration: none;">]</ins>] 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.</div></td></tr>
</table>JaroslavTulachhttp://wiki.apidesign.org/index.php?title=Evolving_the_API_Universe&diff=1308&oldid=prevJaroslavTulach: /* Have You Ever Wondered...? */2008-08-26T19:01:26Z<p><span class="autocomment">Have You Ever Wondered...?</span></p>
<table style="background-color: white; color:black;">
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr>
<td colspan='2' style="background-color: white; color:black;">←Older revision</td>
<td colspan='2' style="background-color: white; color:black;">Revision as of 19:01, 26 August 2008</td>
</tr>
<tr><td colspan="2" class="diff-lineno">Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>== [[Have You Ever Wondered]]...? ==</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>== [[Have You Ever Wondered]]...? ==</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr>
<tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div>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.</div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>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<ins style="color: red; font-weight: bold; text-decoration: none;">. All that is needed is to know the right way of introducing alternative behaviours and also knowing how to allow coexistence of similar APIs</ins>.</div></td></tr>
</table>JaroslavTulachhttp://wiki.apidesign.org/index.php?title=Evolving_the_API_Universe&diff=1281&oldid=prevJaroslavTulach at 19:54, 17 August 20082008-08-17T19:54:09Z<p></p>
<table style="background-color: white; color:black;">
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr>
<td colspan='2' style="background-color: white; color:black;">←Older revision</td>
<td colspan='2' style="background-color: white; color:black;">Revision as of 19:54, 17 August 2008</td>
</tr>
<tr><td colspan="2" class="diff-lineno">Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div><del style="color: red; font-weight: bold; text-decoration: none;">Designing </del>is <del style="color: red; font-weight: bold; text-decoration: none;">done once a time</del>, the <del style="color: red; font-weight: bold; text-decoration: none;">real work in to maintain what we </del>have <del style="color: red; font-weight: bold; text-decoration: none;">designed previously</del>.</div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;">== [[Have You Ever Wondered]]...? ==</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;">Have you ever were afraid to release your API because you knew the implementation behind it </ins>is <ins style="color: red; font-weight: bold; text-decoration: none;">not good enough? Have you been afraid of the API's future? Of numerous bugs</ins>, <ins style="color: red; font-weight: bold; text-decoration: none;">each creating another incompatibility? [[Evolving </ins>the <ins style="color: red; font-weight: bold; text-decoration: none;">API Universe|Chapter 15] explains that you do not </ins>have <ins style="color: red; font-weight: bold; text-decoration: none;">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</ins>.</div></td></tr>
</table>JaroslavTulachhttp://wiki.apidesign.org/index.php?title=Evolving_the_API_Universe&diff=934&oldid=prevApidesign: New page: Designing is done once a time, the real work in to maintain what we have designed previously.2008-06-14T06:23:49Z<p>New page: Designing is done once a time, the real work in to maintain what we have designed previously.</p>
<p><b>New page</b></p><div>Designing is done once a time, the real work in to maintain what we have designed previously.</div>Apidesign