Ticket #396 (closed editorial: incorporated)
editorial improvements to persistent connections section
|Reported by:||email@example.com||Owned by:||firstname.lastname@example.org|
|Component:||p1-messaging||Severity:||In WG Last Call|
6.2. Persistent Connections
I'd mentioned this before on the list, but all the intro text here except for the final "HTTP implementations SHOULD implement persistent connections" is really only of historical interest and could just go away. The "SHOULD implement" requirement could be moved into "6.2.2 Reuse", and then each of the subsections of 6.2 could be promoted up to become a direct child of section 6. So you'd get:
- Connection Management 6.1. Connection 6.2. Establishment 6.3. Reuse 6.3.1. Pipelining 6.3.2. Retrying Requests 6.4. Concurrency 6.5. Failures and Time-outs 6.6. Tear-down 6.7. Upgrade
A server MAY assume that an HTTP/1.1 client intends to maintain a persistent connection until a close connection option is received in a request.