Releases: bearsunday/BEAR.Sunday
1.4.2
1.4.1
1.4.0
1.3.5
1.3.4
1.3.3
1.3.2
- Response http/1.1 304 not modified header in HttpTransfer #122
@kalibora Arigato 👍
1.3.1
1.3.0
Representational State Transfer (REST) 5.1.4 Cache
In order to improve network efficiency, we add cache constraints to form the client-cache-stateless-server style of Section 3.4.4 (Figure 5-4). Cache constraints require that the data within a response to a request be implicitly or explicitly labeled as cacheable or non-cacheable. If a response is cacheable, then a client cache is given the right to reuse that response data for later, equivalent requests.
The advantage of adding cache constraints is that they have the potential to partially or completely eliminate some interactions, improving efficiency, scalability, and user-perceived performance by reducing the average latency of a series of interactions. The trade-off, however, is that a cache can decrease reliability if stale data within the cache differs significantly from the data that would have been obtained had the request been sent directly to the server.
:format(webp)/cdn.vox-cdn.com/uploads/chorus_image/image/61438811/Screen_Shot_2018_09_17_at_9.21.53_PM.0.png)