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

editorial: add introduction for ranges

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p5-range.xml

    r153 r158  
    204204<section title="Introduction" anchor="introduction">
    205205<t>
    206    This document will define aspects of HTTP related to range requests,
    207    partial responses, and the multipart/byteranges media type.  Right now
    208    it only includes the extracted relevant sections of
    209    <xref target="RFC2616">RFC 2616</xref> without edit.
     206   HTTP clients often encounter interrupted data transfers as a result
     207   of cancelled requests or dropped connections.  When a cache has stored
     208   a partial representation, it is desirable to request the remainder
     209   of that representation in a subsequent request rather than transfer
     210   the entire representation.
     211   There are also a number of Web applications that benefit from being
     212   able to request only a subset of a larger representation, such as a
     213   single page of a very large document or only part of an image to be
     214   rendered by a device with limited local storage.
     215</t>
     216<t>
     217   This document defines aspects of HTTP/1.1 related to range requests,
     218   partial responses, and the multipart/byteranges media type.
     219   The protocol for range requests is an &OPTIONAL; feature of HTTP/1.1,
     220   designed so resources or recipients that do not implement this feature
     221   can respond as if it is a normal GET request without impacting
     222   interoperability.  Partial responses are indicated by a distinct status
     223   code to not be mistaken for full responses by intermediate caches
     224   that might not implement the feature.
     225</t>
     226<t>
     227   Although the HTTP/1.1 range request mechanism is designed to allow for
     228   extensible range types, this specification only defines requests for
     229   byte ranges.
    210230</t>
    211231
Note: See TracChangeset for help on using the changeset viewer.