Changeset 2088 for draft-ietf-httpbis/latest/p2-semantics.html

Timestamp:

Jan 5, 2013, 3:42:34 AM (7 years ago)

Author:

fielding@…

Message:

(editorial) Clarify that GET means retrieval; addresses #315

File:

• draft-ietf-httpbis/latest/p2-semantics.html (modified) (2 diffs)

draft-ietf-httpbis/latest/p2-semantics.html

@@ -1387 +1387 @@
       <h3 id="rfc.section.4.3.1"><a href="#rfc.section.4.3.1">4.3.1</a>&nbsp;<a id="GET" href="#GET">GET</a></h3>
       <div id="rfc.iref.g.16"></div>
-      <p id="rfc.section.4.3.1.p.1">The GET method requests transfer of a current representation of the <a href="#resources" class="smpl">target resource</a>.
+      <p id="rfc.section.4.3.1.p.1">The GET method requests transfer of a current representation of the <a href="#resources" class="smpl">target resource</a>. GET is the primary mechanism of information retrieval and the focus of almost all performance optimizations. Hence, when
+         people speak of retrieving some identifiable information via HTTP, they are generally referring to making a GET request.
       </p>
       <p id="rfc.section.4.3.1.p.2">If the target resource is a data-producing process, the produced data will be sent as the representation, not the source text
@@ -1566 +1567 @@
       <p id="rfc.section.4.3.7.p.1">The OPTIONS method requests information about the communication options available on the request/response chain identified
          by the effective request URI. This method allows a client to determine the options and/or requirements associated with a resource,
-         or the capabilities of a server, without implying a resource action or initiating a resource retrieval.
+         or the capabilities of a server, without implying a resource action.
       </p>
       <p id="rfc.section.4.3.7.p.2">Responses to the OPTIONS method are not cacheable.</p>