Changeset 181 for draft-ietf-httpbis/latest/p6-cache.xml

Timestamp:

01/02/08 21:55:09 (13 years ago)

Author:

fielding@…

Message:

editorial: tweak intro to be more direct without former/latter backrefs
and irrelevant details.
Replace typo "resource is cacheable" with "response is cacheable"

File:

• draft-ietf-httpbis/latest/p6-cache.xml (modified) (3 diffs)

draft-ietf-httpbis/latest/p6-cache.xml

@@ -237 +237 @@
 <t>
    Caching would be useless if it did not significantly improve
-   performance. The goal of caching in HTTP/1.1 is to eliminate the need
-   to send requests in many cases, and to eliminate the need to send
-   full responses in many other cases. The former reduces the number of
-   network round-trips required for many operations; we use an
-   "expiration" mechanism for this purpose (see <xref target="expiration.model"/>). The
-   latter reduces network bandwidth requirements; we use a "validation"
-   mechanism for this purpose (see <xref target="validation.model"/>).
+   performance. The goal of caching in HTTP/1.1 is to reuse a prior response
+   message to satisfy a current request.  In some cases, the existing response
+   can be reused without the need for a network request, reducing latency and
+   network round-trips; we use an "expiration" mechanism for this purpose
+   (see <xref target="expiration.model"/>).  Even when a new request is required,
+   it is often possible to reuse all or parts of the payload of a prior response
+   to satisfy the request, thereby reducing network bandwidth usage; we use a
+   "validation" mechanism for this purpose (see <xref target="validation.model"/>).
 </t>
 <iref item="semantically transparent"/>
@@ -251 +252 @@
    requesting client nor the origin server, except to improve
    performance. When a cache is semantically transparent, the client
-   receives exactly the same response (except for hop-by-hop headers)
+   receives exactly the same response status and payload
    that it would have received had its request been handled directly
    by the origin server.
@@ -314 +315 @@
       A response is cacheable if a cache is allowed to store a copy of
       the response message for use in answering subsequent requests.
-      Even if a resource is cacheable, there may
+      Even when a response is cacheable, there may
       be additional constraints on whether a cache can use the cached
       copy for a particular request.