Search results
From APIDesign
You searched for APIDesignPatterns:Evolution
There is no page titled "APIDesignPatterns:Evolution".
For more information about searching APIDesign, see Help.
Showing below up to 20 results starting with #1.
View (previous 20) (next 20) (20 | 50 | 100 | 250 | 500)
No page title matches
Page text matches
- The Future (2,302 bytes)
3: ... for all of us, if our systems were designed with evolution in mind. I hope this book will provoke discussion...
16: ...r coding practices, better libraries and better [[APIDesignPatterns|API Design Patterns]] make tough tasks, originall... - OlderBlogPosts (111,273 bytes)
365: Is [[Builder]] better [[APIDesignPatterns|pattern]] than [[CumulativeFactory]]? As Radim an...
369: ==== Cumulative Factory [[APIDesignPatterns|API Design Pattern]] ====
371: ... [[APIDesignPatterns|API Design Pattern]]. Read [[APIDesignPatterns:CumulativeFactory|more]]...
384: Casper Bang asked following question about [[APIDesignPatterns:Exceptions|exceptions in API]] after reading the ...
388: ...estion! Inspiring. Here are my current answers: [[APIDesignPatterns:Exceptions|exceptions in API]]. - Case Study of Writing the Extensible Visitor Pattern (595 bytes)
3: ...g [[APIDesignPatterns]] - it may not be ready for evolution. For example the well known [[wikipedia::Visitor_... - SignatureTests (3,631 bytes)
42: ...l). We still need a language that will give use [[evolution]] capabilities while letting us act in almost [[c...
51: [[Category:Tools]] [[Category:APIDesignPatterns:Test]] - Evolving the API Universe (1,068 bytes)
3: ...t have to! If you design your API to be ready for evolution, you can resuscitate even bad design of your brok...
5: ...ns [[Singletonizer]], an interesting creational [[APIDesignPatterns|API design pattern]]. However more information is... - RequestResponse (2,479 bytes)
1: [[APIDesignPatterns|API Design pattern]] that solves the problem of g...
5: ==== Evolution Story ====
7: ...o be implemented. From this interface we have two evolution paths:
23: [[Category:APIDesignPatterns]]
24: [[Category:APIDesignPatterns:Evolution]] - Have You Ever Wondered (13,635 bytes)
25: ...mmon worries. It analyses the differences between evolution of APIs targeted to different clients, analyses w...
42: ...t have to! If you design your API to be ready for evolution, you can resuscitate even bad design of your brok...
48: ...g [[APIDesignPatterns]] - it may not be ready for evolution. For example the well known [[wikipedia::Visitor_...
52: ...or all of us, if our systems were designed with [[evolution]] in mind. I hope [[TheAPIBook|this book]] will p... - APIDesignPatterns:Exceptions (8,610 bytes)
29: ...- your options for [[Ever_Changing_Targets|future evolution]] will remain more open.
31: ...rt, exceptions are classes. They shall follow the evolution rules applicable to classes, as discussed in [[Co...
37: ...me Aspects of APIs, from the point of view of API evolution, there is no difference. When a method in a libra...
89: Exceptions are [[APIDesignPatterns:ExceptionExtensibility|easily extensible]] via su...
92: [[Category:APIDesignPatterns]] - ClientAPI (1,758 bytes)
3: ...rence between [[ClientAPI]] and [[ProviderAPI]] [[evolution]] rules. As soon as you publish an [[API]], you, ...
22: [[Category:APIDesignPatterns]]
23: [[Category:APIDesignPatterns:Evolution]] - ProviderAPI (3,010 bytes)
29: [[Category:APIDesignPatterns]]
30: [[Category:APIDesignPatterns:Evolution]] - APIFest08:Report (10,858 bytes)
11: ... me their hacks showing [[BackwardCompatibility]] evolution problems in many solutions.
37: ...r as the solution 07 is based on a variation of [[APIDesignPatterns:RequestResponse|request/response]] pattern, it st... - ExceptionExtensibility (3,165 bytes)
1: It has been mentioned in the [[APIDesignPatterns:Exceptions|page about exceptions]] that changing ...
58: ...ss exposed in the API. This is much more pleasant evolution than for example the one available with [[Talk:Bl...
60: [[Category:APIDesignPatterns]]
61: [[Category:APIDesignPatterns:Evolution]]
62: [[Category:APIDesignPatterns:Exceptions]] - Builder (2,761 bytes)
1: ...''finishing'' the [[API]] calls by final use of [[APIDesignPatterns:Factory|factory method]] makes a lot of sense.
11: ...s can be chained. Alternatively one can use the [[APIDesignPatterns:CumulativeFactory|cumulative factory]] and always...
21: ... characteristics are similar to the ones of the [[APIDesignPatterns:CumulativeFactory|cumulative factory]] pattern. Y...
25: [[Category:APIDesignPatterns]]
26: [[Category:APIDesignPatterns:Creational]] - Factory (898 bytes)
5: This has few benefits from the point of [[API]] [[evolution]]:
6: ... is not subclassable, which solves a lot of nasty evolution problems by itself
12: [[Category:APIDesignPatterns]]
13: [[Category:APIDesignPatterns:Creational]]
14: [[Category:APIDesignPatterns:Encapsulation]] - PropertyFiles (5,584 bytes)
1: ...[[BackwardCompatibility]], be ready for [[API]] [[evolution]], etc.
25: ===== Ready for [[Evolution]] =====
27: ... when designing an [[API]] is to prepare it for [[evolution]]. Why? Because first version is never perfect, y...
29: ...etimes hard to remind ourselves of the need for [[evolution]], especially when we are about to release the fi...
33: ...at point it became clear that there is need for [[evolution]]. It is necessary to indicate whether the [[API]... - AlternativeBehavior (6,943 bytes)
134: [[Category:APIDesignPatterns]]
135: [[Category:APIDesignPatterns:Evolution]] - ClarityOfTypes (6,491 bytes)
42: ...] and moreover they are well set for future, as [[evolution]] story of this pattern is quite good.
44: === Evolution Aspects ===
46: ... of [[DelegationAndComposition]] is useful from [[evolution]] point of view. It is easy to evolve the [[Clien...
48: It is easy to [[evolution|evolve]] the ''Callback'' contract as well. It is...
50: ...rface. But that is quite well thought [[evolution|evolution plan]]. - ImplementOnlyInterface (5,877 bytes)
1: ...able. Each of these [[API]] types has different [[evolution]] characteristics. Also the [[clarity]] of such i...
71: [[Category:APIDesignPatterns]]
72: [[Category:APIDesignPatterns:Clarity]]
73: [[Category:APIDesignPatterns:Creational]] - Adaptable (531 bytes)
11: [[Category:APIDesignPatterns]]
12: [[Category:APIDesignPatterns:Evolution]] - ClearDefinitionOfVersion (1,810 bytes)
19: This is one of [[APIDesignPatterns|the patterns]] where usage of [[Java]] interfaces...
21: [[Category:APIDesignPatterns:Clarity]]
22: [[Category:APIDesignPatterns:Evolution]]
View (previous 20) (next 20) (20 | 50 | 100 | 250 | 500)
Follow
