Changeset 181 for draft-ietf-httpbis/latest/p6-cache.xml
- Timestamp:
- 01/02/08 21:55:09 (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.xml
r173 r181 237 237 <t> 238 238 Caching would be useless if it did not significantly improve 239 performance. The goal of caching in HTTP/1.1 is to eliminate the need 240 to send requests in many cases, and to eliminate the need to send 241 full responses in many other cases. The former reduces the number of 242 network round-trips required for many operations; we use an 243 "expiration" mechanism for this purpose (see <xref target="expiration.model"/>). The 244 latter reduces network bandwidth requirements; we use a "validation" 245 mechanism for this purpose (see <xref target="validation.model"/>). 239 performance. The goal of caching in HTTP/1.1 is to reuse a prior response 240 message to satisfy a current request. In some cases, the existing response 241 can be reused without the need for a network request, reducing latency and 242 network round-trips; we use an "expiration" mechanism for this purpose 243 (see <xref target="expiration.model"/>). Even when a new request is required, 244 it is often possible to reuse all or parts of the payload of a prior response 245 to satisfy the request, thereby reducing network bandwidth usage; we use a 246 "validation" mechanism for this purpose (see <xref target="validation.model"/>). 246 247 </t> 247 248 <iref item="semantically transparent"/> … … 251 252 requesting client nor the origin server, except to improve 252 253 performance. When a cache is semantically transparent, the client 253 receives exactly the same response (except for hop-by-hop headers)254 receives exactly the same response status and payload 254 255 that it would have received had its request been handled directly 255 256 by the origin server. … … 314 315 A response is cacheable if a cache is allowed to store a copy of 315 316 the response message for use in answering subsequent requests. 316 Even if a resource is cacheable, there may317 Even when a response is cacheable, there may 317 318 be additional constraints on whether a cache can use the cached 318 319 copy for a particular request.
Note: See TracChangeset
for help on using the changeset viewer.