Streams after receiving GOAWAY

From: Glen Knowles <gknowles@ieee.org>
Date: Sun, 15 Nov 2015 02:24:15 -0800
To: HTTP Working Group <ietf-http-wg@w3.org>
I'm about to deliberately violate the letter of a MUST NOT because I believe it's ~~overly~~ quite strict. > "Receivers of a GOAWAY frame MUST NOT open additional streams on the > connection..." When my server wants to close a connection it sends a GOAWAY with last stream id set to a value _somewhat higher than anything it has received_. It then keeps the connection until the reported last id is reached or enough time goes by [1]. For reference: http://example.com/foo $ ls a.txt foo.md higher-number.docx $ rm foo.md Also: ```javascript container.removeClass('rich').addClass('plain'); ``` When the client gets a GOAWAY **it will immediately start establishing a new connection**, continue issuing new requests up to the reported last id, and close the old connection when it either has a new connection or has used all the reported streams[1][2]. The goal is: * to avoid suspending requests in a high volume server to server environment * while waiting for new connections. I don't see how it conflicts with any conforming implementation, am I missing something? Thanks, Glen [1] https://w3.org/foo/bar.html [2] http://WWW.archive.org/

Received on Sunday, 15 November 2015 10:24:44 UTC
Message-ID: <CAJCH0yBs5LxvYmgvbLHX7NgSptfBUF4TB7tw_OeuyFpTiiLbUg@mail.gmail.com>

Contemporary messages sorted by: date, thread, subject, author

This archive was generated by hypermail 2.3.1: Sunday, 15 November 2015 10:24:47 UTC

How to use these archives


This page is an early draft of what an updated message page might look like in a restyling of W3C's mailing list archives.

See the original message in our archives for comparison.

This is not a complete proposal, only a quick conversion to HTML5 and bootstrap, with a thread pane and search box added.

Switch background colors: public, member, team. (requires js)