Changeset 899


Ignore:
Timestamp:
Jul 23, 2010, 11:33:10 PM (9 years ago)
Author:
fielding@…
Message:

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

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r881 r899  
    544544</section>
    545545
    546 <section title="HTTP architecture" anchor="architecture">
     546<section title="HTTP-related architecture" anchor="architecture">
    547547<t>
    548548   HTTP was created for the World Wide Web architecture
     
    552552</t>
    553553
    554 <section title="Client/Server Operation" anchor="operation">
     554<section title="Client/Server Messaging" anchor="operation">
    555555<iref item="client"/>
    556556<iref item="server"/>
    557557<iref item="connection"/>
    558558<t>
    559    HTTP is a request/response protocol that operates by exchanging messages
    560    across a reliable transport or session-layer connection. An HTTP client
    561    is a program that establishes a connection to a server for the purpose
    562    of sending one or more HTTP requests.  An HTTP server is a program that
    563    accepts connections in order to service HTTP requests by sending HTTP
    564    responses.
     559   HTTP is a stateless request/response protocol that operates by exchanging
     560   messages across a reliable transport or session-layer connection. An HTTP
     561   "client" is a program that establishes a connection to a server for the
     562   purpose of sending one or more HTTP requests.  An HTTP "server" is a
     563   program that accepts connections in order to service HTTP requests by
     564   sending HTTP responses.
    565565</t>
    566566<iref item="user agent"/>
    567567<iref item="origin server"/>
    568568<t>
    569    Note that the terms "client" and "server" refer only to the roles that
     569   Note that the terms client and server refer only to the roles that
    570570   these programs perform for a particular connection.  The same program
    571571   may act as a client on some connections and a server on others.  We use
     
    578578   Most HTTP communication consists of a retrieval request (GET) for
    579579   a representation of some resource identified by a URI.  In the
    580    simplest case, this may be accomplished via a single connection (v)
    581    between the user agent (UA) and the origin server (O).
     580   simplest case, this may be accomplished via a single bidirectional
     581   connection (===) between the user agent (UA) and the origin server (O).
    582582</t>
    583583<figure><artwork type="drawing">
    584        request chain ------------------------&gt;
    585     UA -------------------v------------------- O
    586        &lt;----------------------- response chain
     584         request   &gt;
     585    UA ======================================= O
     586                                &lt;   response
    587587</artwork></figure>
    588588<iref item="message"/>
     
    644644</t>
    645645<figure><artwork type="drawing">
    646        request chain --------------------------------------&gt;
    647     UA -----v----- A -----v----- B -----v----- C -----v----- O
    648        &lt;------------------------------------- response chain
     646         &gt;             &gt;             &gt;             &gt;
     647    UA =========== A =========== B =========== C =========== O
     648               &lt;             &lt;             &lt;             &lt;
    649649</artwork></figure>
    650650<t>
     
    672672</t>
    673673<t><iref item="proxy"/>
    674    A proxy is a message forwarding agent that is selected by the
     674   A "proxy" is a message forwarding agent that is selected by the
    675675   client, usually via local configuration rules, to receive requests
    676676   for some type(s) of absolute URI and attempt to satisfy those
     
    683683</t>
    684684<t><iref item="gateway"/><iref item="reverse proxy"/>
    685    A gateway (a.k.a., reverse proxy) is a receiving agent that acts
     685   A "gateway" (a.k.a., "reverse proxy") is a receiving agent that acts
    686686   as a layer above some other server(s) and translates the received
    687687   requests to the underlying server's protocol.  Gateways are often
     
    699699</t>
    700700<t><iref item="tunnel"/>
    701    A tunnel acts as a blind relay between two connections
     701   A "tunnel" acts as a blind relay between two connections
    702702   without changing the messages. Once active, a tunnel is not
    703703   considered a party to the HTTP communication, though the tunnel may
     
    715715   Any party to HTTP communication that is not acting as a tunnel may
    716716   employ an internal cache for handling requests.
    717    A cache is a local store of previous response messages and the
     717   A "cache" is a local store of previous response messages and the
    718718   subsystem that controls its message storage, retrieval, and deletion.
    719719   A cache stores cacheable responses in order to reduce the response
     
    730730</t>
    731731<figure><artwork type="drawing">
    732           request chain ----------&gt;
    733        UA -----v----- A -----v----- B - - - - - - C - - - - - - O
    734           &lt;--------- response chain
     732            &gt;             &gt;
     733       UA =========== A =========== B - - - - - - C - - - - - - O
     734                  &lt;             &lt;
    735735</artwork></figure>
    736736<t><iref item="cacheable"/>
    737    A response is cacheable if a cache is allowed to store a copy of
     737   A response is "cacheable" if a cache is allowed to store a copy of
    738738   the response message for use in answering subsequent requests.
    739739   Even when a response is cacheable, there may be additional
Note: See TracChangeset for help on using the changeset viewer.