HTTP Cache Responder
Rails has embraced REST since version 1.2, and since then, developing APIs has become easier and easier. However, as your application grows, you may have to focus more on your API implementation and find ways to optimize the number of requests it can handle.
When you expose an API, it’s common that a client requests a resource to the server several times, and the client always gets the same response back since the requested resource has not changed. In these cases, the server is wasting time rendering the same resource all over again, and the client is parsing the same response just to find out that nothing has changed.
Luckily, the HTTP 1.1 specification has a section dedicated to caching. The previous problem could ...
Get Crafting Rails 4 Applications, 2nd Edition now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
