Ignore:
Timestamp:
Jul 22, 2010, 2:06:27 AM (9 years ago)
Author:
fielding@…
Message:

Addresses #109: Clarify entity / representation / variant terminology

Replaced entity with representation.

File:
1 edited

Legend:

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

    r863 r866  
    419419</t>
    420420<t>
    421    If a cache has a stored non-empty set of subranges for an entity, and
     421   If a cache has a stored non-empty set of subranges for a representation, and
    422422   an incoming response transfers another subrange, the cache &MAY;
    423423   combine the new subrange with the existing set if both the following
     
    445445<t>
    446446   For entity-header fields, both sender and recipient refer to either the
    447    client or the server, depending on who sends and who receives the entity.
     447   client or the server, depending on who sends and who receives the message.
    448448</t>
    449449
     
    549549</t>
    550550<t>
    551    Examples of byte-content-range-spec values, assuming that the entity
     551   Examples of byte-content-range-spec values, assuming that the representation
    552552   contains a total of 1234 bytes:
    553553   <list style="symbols">
     
    647647   could use the Range request-header with a conditional GET (using
    648648   either or both of If-Unmodified-Since and If-Match.) However, if the
    649    condition fails because the entity has been modified, the client
     649   condition fails because the representation has been modified, the client
    650650   would then have to make a second request to obtain the entire current
    651    entity-body.
     651   representation.
    652652</t>
    653653<t>
    654654   The "If-Range" request-header field allows a client to "short-circuit" the second
    655    request. Informally, its meaning is "if the entity is unchanged, send
     655   request. Informally, its meaning is "if the representation is unchanged, send
    656656   me the part(s) that I am missing; otherwise, send me the entire new
    657    entity".
     657   representation".
    658658</t>
    659659<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="If-Range"/><iref primary="true" item="Grammar" subitem="If-Range-v"/>
     
    662662</artwork></figure>
    663663<t>
    664    If the client has no entity tag for an entity, but does have a Last-Modified
     664   If the client has no entity tag for a representation, but does have a Last-Modified
    665665   date, it &MAY; use that date in an If-Range header. (The
    666666   server can distinguish between a valid HTTP-date and any form of
     
    672672<t>
    673673   If the entity tag given in the If-Range header matches the current
    674    cache validator for the entity, then the server &SHOULD; provide the
    675    specified sub-range of the entity using a 206 (Partial Content)
     674   cache validator for the representation, then the server &SHOULD; provide the
     675   specified sub-range of the representation using a 206 (Partial Content)
    676676   response. If the cache validator does not match, then the server &SHOULD;
    677    return the entire entity using a 200 (OK) response.
     677   return the entire representation using a 200 (OK) response.
    678678</t>
    679679</section>
     
    685685<section title="Byte Ranges" anchor="byte.ranges">
    686686<t>
    687    Since all HTTP entities are represented in HTTP messages as sequences
     687   Since all HTTP representations are transferred as sequences
    688688   of bytes, the concept of a byte range is meaningful for any HTTP
    689    entity. (However, not all clients and servers need to support byte-range
     689   representation. (However, not all clients and servers need to support byte-range
    690690   operations.)
    691691</t>
    692692<t>
    693693   Byte range specifications in HTTP apply to the sequence of bytes in
    694    the entity-body (not necessarily the same as the message-body).
     694   the representation body (not necessarily the same as the message-body).
    695695</t>
    696696<t anchor="rule.ranges-specifier">
     
    705705
    706706   A byte range operation &MAY; specify a single range of bytes, or a set
    707    of ranges within a single entity.
     707   of ranges within a single representation.
    708708</t>
    709709<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="ranges-specifier"/><iref primary="true" item="Grammar" subitem="byte-ranges-specifier"/><iref primary="true" item="Grammar" subitem="byte-range-set"/><iref primary="true" item="Grammar" subitem="byte-range-spec"/><iref primary="true" item="Grammar" subitem="first-byte-pos"/><iref primary="true" item="Grammar" subitem="last-byte-pos"/>
     
    729729<t>
    730730   If the last-byte-pos value is absent, or if the value is greater than
    731    or equal to the current length of the entity-body, last-byte-pos is
    732    taken to be equal to one less than the current length of the entity-body
     731   or equal to the current length of the representation body, last-byte-pos is
     732   taken to be equal to one less than the current length of the representation
    733733   in bytes.
    734734</t>
    735735<t>
    736736   By its choice of last-byte-pos, a client can limit the number of
    737    bytes retrieved without knowing the size of the entity.
     737   bytes retrieved without knowing the size of the representation.
    738738</t>
    739739<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="suffix-byte-range-spec"/><iref primary="true" item="Grammar" subitem="suffix-length"/>
     
    743743<t>
    744744   A suffix-byte-range-spec is used to specify the suffix of the
    745    entity-body, of a length given by the suffix-length value. (That is,
     745   representation body, of a length given by the suffix-length value. (That is,
    746746   this form specifies the last N bytes of an entity-body.) If the
    747    entity is shorter than the specified suffix-length, the entire
    748    entity-body is used.
     747   representation is shorter than the specified suffix-length, the entire
     748   representation is used.
    749749</t>
    750750<t>
     
    757757   of 416 (Requested range not satisfiable). Otherwise, the server
    758758   &SHOULD; return a response with a status of 206 (Partial Content)
    759    containing the satisfiable ranges of the entity-body.
     759   containing the satisfiable ranges of the representation.
    760760</t>
    761761<t>
     
    805805<t>
    806806   The "Range" request-header field defines the GET method (conditional or
    807    not) to request one or more sub-ranges of the response entity-body, instead
    808    of the entire entity body.
     807   not) to request one or more sub-ranges of the response representation body, instead
     808   of the entire representation body.
    809809</t>
    810810<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Range"/>
     
    12871287      Notes:
    12881288  <list style="numbers">
    1289       <t>Additional CRLFs may precede the first boundary string in the
    1290          entity.</t>
     1289      <t>Additional CRLFs may precede the first boundary string in the body.</t>
    12911290
    12921291      <t>Although <xref target="RFC2046"/> permits the boundary string to be
Note: See TracChangeset for help on using the changeset viewer.