Ignore:
Timestamp:
Mar 6, 2009, 8:52:15 PM (11 years ago)
Author:
fielding@…
Message:

editorial: another pass at intro streamlining, removed unnecessary
references to FTP, Gopher, NNTP, and WAIS.

File:
1 edited

Legend:

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

    r543 r544  
    231231   message payloads for flexible interaction with network-based hypertext
    232232   information systems. HTTP relies upon the Uniform Resource Identifier (URI)
    233    standard <xref target="RFC3986"/> to indicate resource targets and
     233   standard <xref target="RFC3986"/> to indicate request targets and
    234234   relationships between resources.
    235235   Messages are passed in a format similar to that used by Internet mail
     
    239239</t>
    240240<t>
    241    HTTP is a generic interface protocol for informations systems. It is
     241   HTTP is a generic interface protocol for information systems. It is
    242242   designed to hide the details of how a service is implemented by presenting
    243243   a uniform interface to clients that is independent of the types of
     
    251251<t>
    252252   HTTP is also designed for use as a generic protocol for translating
    253    communication to and from other Internet information systems, such as
    254    USENET news services via NNTP <xref target="RFC3977"/>,
    255    file services via FTP <xref target="RFC959"/>,
    256    Gopher <xref target="RFC1436"/>, and WAIS <xref target="WAIS"/>.
     253   communication to and from other Internet information systems.
    257254   HTTP proxies and gateways provide access to alternative information
    258255   services by translating their diverse protocols into a hypertext
     
    261258</t>
    262259<t>
    263    One consequence of HTTP flexibility is that the protocol cannot be defined
    264    in terms of what occurs behind the interface. Instead, we are
    265    limited to defining the syntax of communication, the intent
    266    of received communication, and the expected behavior of recipients. If
    267    the communication is considered in isolation, then successful actions
    268    should be reflected in the observable interface provided by servers.
    269    However, since many clients are potentially acting in parallel and
    270    perhaps at cross-purposes, it would be meaningless to require that such
    271    behavior be observable.
     260   One consequence of HTTP flexibility is that the protocol cannot be
     261   defined in terms of what occurs behind the interface. Instead, we
     262   are limited to defining the syntax of communication, the intent
     263   of received communication, and the expected behavior of recipients.
     264   If the communication is considered in isolation, then successful
     265   actions should be reflected in corresponding changes to the
     266   observable interface provided by servers. However, since multiple
     267   clients may act in parallel and perhaps at cross-purposes, we
     268   cannot require that such changes be observable beyond the scope
     269   of a single response.
    272270</t>
    273271<t>
     
    275273   defining the protocol referred to as "HTTP/1.1" and obsoleting
    276274   <xref target="RFC2616"/>.
    277    Part 1 defines the URI schemes specific to HTTP-based resources, overall
    278    network operation, transport protocol connection management, and HTTP
    279    message framing and forwarding requirements.
     275   Part 1 describes the architectural elements that are used or
     276   referred to in HTTP and defines the URI schemes specific to
     277   HTTP-based resources, overall network operation, connection
     278   management, and HTTP message framing and forwarding requirements.
    280279   Our goal is to define all of the mechanisms necessary for HTTP message
    281280   handling that are independent of message semantics, thereby defining the
    282    complete set of requirements for a message parser and transparent
     281   complete set of requirements for message parsers and
    283282   message-forwarding intermediaries.
    284283</t>
     
    34813480</reference>
    34823481
    3483 <reference anchor="RFC959">
    3484   <front>
    3485     <title abbrev="File Transfer Protocol">File Transfer Protocol</title>
    3486     <author initials="J." surname="Postel" fullname="J. Postel">
    3487       <organization>Information Sciences Institute (ISI)</organization>
    3488     </author>
    3489     <author initials="J." surname="Reynolds" fullname="J. Reynolds">
    3490       <organization/>
    3491     </author>
    3492     <date month="October" year="1985"/>
    3493   </front>
    3494   <seriesInfo name="STD" value="9"/>
    3495   <seriesInfo name="RFC" value="959"/>
    3496 </reference>
    3497 
    34983482<reference anchor="RFC1123">
    34993483  <front>
     
    35213505</reference>
    35223506
    3523 <reference anchor="RFC1436">
    3524   <front>
    3525     <title abbrev="Gopher">The Internet Gopher Protocol (a distributed document search and retrieval protocol)</title>
    3526     <author initials="F." surname="Anklesaria" fullname="Farhad Anklesaria">
    3527       <organization>University of Minnesota, Computer and Information Services</organization>
    3528       <address><email>fxa@boombox.micro.umn.edu</email></address>
    3529     </author>
    3530     <author initials="M." surname="McCahill" fullname="Mark McCahill">
    3531       <organization>University of Minnesota, Computer and Information Services</organization>
    3532       <address><email>mpm@boombox.micro.umn.edu</email></address>
    3533     </author>
    3534     <author initials="P." surname="Lindner" fullname="Paul Lindner">
    3535       <organization>University of Minnesota, Computer and Information Services</organization>
    3536       <address><email>lindner@boombox.micro.umn.edu</email></address>
    3537     </author>
    3538     <author initials="D." surname="Johnson" fullname="David Johnson">
    3539       <organization>University of Minnesota, Computer and Information Services</organization>
    3540       <address><email>dmj@boombox.micro.umn.edu</email></address>
    3541     </author>
    3542     <author initials="D." surname="Torrey" fullname="Daniel Torrey">
    3543       <organization>University of Minnesota, Computer and Information Services</organization>
    3544       <address><email>daniel@boombox.micro.umn.edu</email></address>
    3545     </author>
    3546     <author initials="B." surname="Alberti" fullname="Bob Alberti">
    3547       <organization>University of Minnesota, Computer and Information Services</organization>
    3548       <address><email>alberti@boombox.micro.umn.edu</email></address>
    3549     </author>
    3550     <date month="March" year="1993"/>
    3551   </front>
    3552   <seriesInfo name="RFC" value="1436"/>
    3553 </reference>
    3554 
    35553507<reference anchor="RFC1900">
    35563508  <front>
     
    37683720  <seriesInfo name='BCP' value='90' />
    37693721  <seriesInfo name='RFC' value='3864' />
    3770 </reference>
    3771 
    3772 <reference anchor='RFC3977'>
    3773   <front>
    3774     <title>Network News Transfer Protocol (NNTP)</title>
    3775     <author initials='C.' surname='Feather' fullname='C. Feather'>
    3776       <organization>THUS plc</organization>
    3777       <address><email>clive@demon.net</email></address>
    3778     </author>
    3779     <date year='2006' month='October' />
    3780   </front>
    3781   <seriesInfo name="RFC" value="3977"/>
    37823722</reference>
    37833723
     
    38833823</reference>
    38843824
    3885 <reference anchor="WAIS">
    3886   <front>
    3887     <title>WAIS Interface Protocol Prototype Functional Specification (v1.5)</title>
    3888     <author initials="F." surname="Davis" fullname="F. Davis">
    3889       <organization>Thinking Machines Corporation</organization>
    3890     </author>
    3891     <author initials="B." surname="Kahle" fullname="B. Kahle">
    3892       <organization>Thinking Machines Corporation</organization>
    3893     </author>
    3894     <author initials="H." surname="Morris" fullname="H. Morris">
    3895       <organization>Thinking Machines Corporation</organization>
    3896     </author>
    3897     <author initials="J." surname="Salem" fullname="J. Salem">
    3898       <organization>Thinking Machines Corporation</organization>
    3899     </author>
    3900     <author initials="T." surname="Shen" fullname="T. Shen">
    3901       <organization>Thinking Machines Corporation</organization>
    3902     </author>
    3903     <author initials="R." surname="Wang" fullname="R. Wang">
    3904       <organization>Thinking Machines Corporation</organization>
    3905     </author>
    3906     <author initials="J." surname="Sui" fullname="J. Sui">
    3907       <organization>Thinking Machines Corporation</organization>
    3908     </author>
    3909     <author initials="M." surname="Grinbaum" fullname="M. Grinbaum">
    3910       <organization>Thinking Machines Corporation</organization>
    3911     </author>
    3912     <date month="April" year="1990"/>
    3913   </front>
    3914   <seriesInfo name="Thinking Machines Corporation" value=""/>
    3915 </reference>
    3916 
    39173825</references>
    39183826
Note: See TracChangeset for help on using the changeset viewer.