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