Changeset 2005 for draft-ietf-httpbis/latest/p1-messaging.xml

Timestamp:

28/11/12 08:21:03 (9 years ago)

Author:

fielding@…

Message:

remove bogus (non-interop) requirement on being able to recover from asynchronous close events

File:

• draft-ietf-httpbis/latest/p1-messaging.xml (modified) (1 diff)

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

@@ -2903 +2903 @@
 <section title="Retrying Requests" anchor="persistent.retrying.requests">
 <t>
-   Senders can close the transport connection at any time. Therefore, 
-   clients, servers, and proxies &MUST; be able to recover
-   from asynchronous close events. Client software &MAY; reopen the
-   transport connection and retransmit the aborted sequence of requests
-   without user interaction so long as the request sequence is
-   idempotent (see &idempotent-methods;). Non-idempotent request methods or sequences
-   &MUST-NOT; be automatically retried, although user agents &MAY; offer a
-   human operator the choice of retrying the request(s). Confirmation by
+   Connections can be closed at any time, with or without intention.
+   Implementations ought to anticipate the need to recover
+   from asynchronous close events.
+   A client &MAY; open a new connection and retransmit an aborted sequence
+   of requests without user interaction so long as the request sequence is
+   idempotent (see &idempotent-methods;).
+   A client &MUST-NOT; automatically retry non-idempotent request sequences,
+   although user agents &MAY; offer a human operator the choice of retrying
+   the request(s). Confirmation by
    user agent software with semantic understanding of the application
-   &MAY; substitute for user confirmation. The automatic retry &SHOULD-NOT; 
-   be repeated if the second sequence of requests fails.
+   &MAY; substitute for user confirmation. An automatic retry &SHOULD-NOT; 
+   be repeated if a second sequence of requests fails.
 </t>
 </section>