APIDesignPatterns

From APIDesign

(Difference between revisions)
Jump to: navigation, search
(API Design Patterns)
Line 1: Line 1:
-
== API Design Patterns ==
+
[[APIDesignPatterns|API Design Patterns]] are classical [[wikipedia::Design_patterns|design patterns]] with a special emphasis on evolution. They are essential for creation of shared libraries and frameworks that can be evolved over the time in proper, [[BackwardCompatibility|compatible]] way. Many of them are discussed in [[TheAPIBook]], however as time evolves, and as our knowledge is growing, additional observations are discovered. That is why here you can find up-to-date list:
-
Are [[wikipedia::Design_patterns]] with a special emphasis on evolution. They are essential for creation of shared libraries and frameworks that can be evolved over the time in proper, compatible way. Many of them are discussed in [[TheAPIBook]], however as time evolves, and our knowledge is growing, here are additional observations that didn't make it into [[TheAPIBook]]:
 
* [[APIDesignPatterns:ResponseReply]]
* [[APIDesignPatterns:ResponseReply]]
* [[APIDesignPatterns:Exceptions|Using Exceptions while designing APIs]]
* [[APIDesignPatterns:Exceptions|Using Exceptions while designing APIs]]

Revision as of 19:14, 22 October 2008

API Design Patterns are classical design patterns with a special emphasis on evolution. They are essential for creation of shared libraries and frameworks that can be evolved over the time in proper, compatible way. Many of them are discussed in TheAPIBook, however as time evolves, and as our knowledge is growing, additional observations are discovered. That is why here you can find up-to-date list:


Personal tools
buy