Changeset 899

Timestamp:

24/07/10 06:33:10 (12 years ago)

Author:

fielding@…

Message:

(editorial) Improve my ascii art and
quote significant terms where they are first defined.

File:

• draft-ietf-httpbis/latest/p1-messaging.xml (modified) (9 diffs)

draft-ietf-httpbis/latest/p1-messaging.xml

@@ -544 +544 @@
 </section>
 
-<section title="HTTP architecture" anchor="architecture">
+<section title="HTTP-related architecture" anchor="architecture">
 <t>
    HTTP was created for the World Wide Web architecture
@@ -552 +552 @@
 </t>
 
-<section title="Client/Server Operation" anchor="operation">
+<section title="Client/Server Messaging" anchor="operation">
 <iref item="client"/>
 <iref item="server"/>
 <iref item="connection"/>
 <t>
-   HTTP is a request/response protocol that operates by exchanging messages
-   across a reliable transport or session-layer connection. An HTTP client
-   is a program that establishes a connection to a server for the purpose
-   of sending one or more HTTP requests.  An HTTP server is a program that
-   accepts connections in order to service HTTP requests by sending HTTP
-   responses.
+   HTTP is a stateless request/response protocol that operates by exchanging
+   messages across a reliable transport or session-layer connection. An HTTP
+   "client" is a program that establishes a connection to a server for the
+   purpose of sending one or more HTTP requests.  An HTTP "server" is a
+   program that accepts connections in order to service HTTP requests by
+   sending HTTP responses.
 </t>
 <iref item="user agent"/>
 <iref item="origin server"/>
 <t>
-   Note that the terms "client" and "server" refer only to the roles that
+   Note that the terms client and server refer only to the roles that
    these programs perform for a particular connection.  The same program
    may act as a client on some connections and a server on others.  We use
@@ -578 +578 @@
    Most HTTP communication consists of a retrieval request (GET) for
    a representation of some resource identified by a URI.  In the
-   simplest case, this may be accomplished via a single connection (v)
-   between the user agent (UA) and the origin server (O).
+   simplest case, this may be accomplished via a single bidirectional
+   connection (===) between the user agent (UA) and the origin server (O).
 </t>
 <figure><artwork type="drawing">
-       request chain ------------------------&gt;
-    UA -------------------v------------------- O
-       &lt;----------------------- response chain
+         request   &gt;
+    UA ======================================= O
+                                &lt;   response
 </artwork></figure>
 <iref item="message"/>
@@ -644 +644 @@
 </t>
 <figure><artwork type="drawing">
-       request chain --------------------------------------&gt;
-    UA -----v----- A -----v----- B -----v----- C -----v----- O
-       &lt;------------------------------------- response chain
+         &gt;             &gt;             &gt;             &gt;
+    UA =========== A =========== B =========== C =========== O
+               &lt;             &lt;             &lt;             &lt;
 </artwork></figure>
 <t>
@@ -672 +672 @@
 </t>
 <t><iref item="proxy"/>
-   A proxy is a message forwarding agent that is selected by the
+   A "proxy" is a message forwarding agent that is selected by the
    client, usually via local configuration rules, to receive requests
    for some type(s) of absolute URI and attempt to satisfy those
@@ -683 +683 @@
 </t>
 <t><iref item="gateway"/><iref item="reverse proxy"/>
-   A gateway (a.k.a., reverse proxy) is a receiving agent that acts
+   A "gateway" (a.k.a., "reverse proxy") is a receiving agent that acts
    as a layer above some other server(s) and translates the received
    requests to the underlying server's protocol.  Gateways are often
@@ -699 +699 @@
 </t>
 <t><iref item="tunnel"/>
-   A tunnel acts as a blind relay between two connections
+   A "tunnel" acts as a blind relay between two connections
    without changing the messages. Once active, a tunnel is not
    considered a party to the HTTP communication, though the tunnel may
@@ -715 +715 @@
    Any party to HTTP communication that is not acting as a tunnel may
    employ an internal cache for handling requests.
-   A cache is a local store of previous response messages and the
+   A "cache" is a local store of previous response messages and the
    subsystem that controls its message storage, retrieval, and deletion.
    A cache stores cacheable responses in order to reduce the response
@@ -730 +730 @@
 </t>
 <figure><artwork type="drawing">
-          request chain ----------&gt;
-       UA -----v----- A -----v----- B - - - - - - C - - - - - - O
-          &lt;--------- response chain
+            &gt;             &gt;
+       UA =========== A =========== B - - - - - - C - - - - - - O
+                  &lt;             &lt;
 </artwork></figure>
 <t><iref item="cacheable"/>
-   A response is cacheable if a cache is allowed to store a copy of
+   A response is "cacheable" if a cache is allowed to store a copy of
    the response message for use in answering subsequent requests.
    Even when a response is cacheable, there may be additional