Andrew Godwin

You'll notice that nothing async happens in the constructor, it happens in `get_response` (including sending the request to the backend), including sending the request to the app in the first...

Hm, one problem with this is that the ASGI events are deliberately limited to a JSON-plus-bytes-type set of potential values; passing a full object like this is sort of difficult...

Right, I think some level of that information would be a useful _optional extra_ to the scope for servers to provide, though like with the raw path info, it's impossible...

This ticket is basically awaiting someone to sit down and fully write out the spec as a pull request, so we can get direct feedback on the format.

Any contribution to the testing docs would be welcome!

Yes, this is mostly a legacy of the asgiref docs actually being the ASGI specification website. We should get around to fixing this.

To clarify a bit more - this ticket will just be for graceful shutdown (connection draining), as restarting/reloading is much more complicated and will require us to do things with...

Graceful shutdown is mostly so you can prevent new connections while you close out old ones, which is especially useful for WebSockets, which are more stateful than HTTP. New Linux...

As discussed on #182, `SO_REUSEPORT` is unfortunately not going to be easy in the short term, so instead we'll have to rely on people using the `--fd` option with process...

It won't until I implement it, which is why this ticket is still open. Right now it will just hard-exit.