APIDesignPatterns
From APIDesign
(Difference between revisions)
| Line 4: | Line 4: | ||
* [[APIDesignPatterns:RequestResponse|Request/Response]] | * [[APIDesignPatterns:RequestResponse|Request/Response]] | ||
* [[APIDesignPatterns:Exceptions|Using Exceptions while designing APIs]] | * [[APIDesignPatterns:Exceptions|Using Exceptions while designing APIs]] | ||
| + | * [[APIDesignPatterns:ExceptionExtensibility|Extensibility of Exceptions]] | ||
* [[APIDesignPatterns:ClientAPI|Growing Client API]] | * [[APIDesignPatterns:ClientAPI|Growing Client API]] | ||
* [[APIDesignPatterns:ProviderAPI|Growing Provider API]] | * [[APIDesignPatterns:ProviderAPI|Growing Provider API]] | ||
* [[APIDesignPatterns:FriendPackages|Friend Packages]] | * [[APIDesignPatterns:FriendPackages|Friend Packages]] | ||
* [[APIDesignPatterns::GetterAndSetter|Use Getter and Setters]] | * [[APIDesignPatterns::GetterAndSetter|Use Getter and Setters]] | ||
Revision as of 18:12, 8 November 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:
Follow
