Category:APIDesignPatterns:Performance
From APIDesign
(Difference between revisions)
(New page: Designing APIs to have good performance - e.g. to execute quickly, and not over-consume various resources - is harder than optimizing a single in-house application. Here is few tri...) |
|||
| Line 1: | Line 1: | ||
Designing [[API]]s to have good [[performance]] - e.g. to execute quickly, and not over-consume various resources - is harder than optimizing a single in-house application. Here is few tricks to make it easier. | Designing [[API]]s to have good [[performance]] - e.g. to execute quickly, and not over-consume various resources - is harder than optimizing a single in-house application. Here is few tricks to make it easier. | ||
| + | |||
| + | [[Category:APIDesignPatterns]] | ||
Revision as of 17:40, 4 February 2010
Designing APIs to have good performance - e.g. to execute quickly, and not over-consume various resources - is harder than optimizing a single in-house application. Here is few tricks to make it easier.
Pages in category "APIDesignPatterns:Performance"
There are 3 pages in this category.
Follow
