Ignore:
Timestamp:
Jan 11, 2008, 9:09:10 PM (12 years ago)
Author:
fielding@…
Message:

editorial: make introductions more active and consistent

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p6-cache.html

    r157 r163  
    573573      </ul>
    574574      <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="caching" href="#caching">Introduction</a></h1>
    575       <p id="rfc.section.1.p.1">HTTP is typically used for distributed information systems, where performance can be improved by the use of response caches.
    576          The HTTP/1.1 protocol includes a number of elements intended to make caching work as well as possible. Because these elements
    577          are inextricable from other aspects of the protocol, and because they interact with each other, it is useful to describe the
    578          basic caching design of HTTP separately from the detailed descriptions of methods, headers, response codes, etc. This document
    579          defines aspects of HTTP related to caching response messages.
     575      <p id="rfc.section.1.p.1">HTTP is typically used for distributed information systems, where performance can be improved by the use of response caches,
     576         and includes a number of elements intended to make caching work as well as possible. Because these elements interact with
     577         each other, it is useful to describe the caching design of HTTP separately. This document defines aspects of HTTP/1.1 related
     578         to caching and reusing response messages.
    580579      </p>
    581580      <div id="rfc.iref.c.1"></div>
Note: See TracChangeset for help on using the changeset viewer.