/explore
|
You are here 
|
techblog.thescore.com | ||
| | | | |
www.speakeasy.com
Designing an API with cacheability in mind produces a more sensible and better separated set of resources, and it just so happens to be more performant, cheaper, and better for the environment. |
|
| | | | | ||
| | | | |
humanwhocodes.com
The Official Web Site of Nicholas C. Zakas |
|
| | | | | ||
| | | | |
openapi.com
HTTP status codes in API responses: what they are and what they mean |
|
| | | | | ||
| | | | |
www.mnot.net
A long, long time ago, I wrote some tests using XmlHttpRequest to figure out how well browser caches behaved, and wrote up the results. |
|
| | | |||
