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/