Andrew Godwin

I'd be happy to take a pull request or docs to make this better. I agree other servers implement this - most also have bigger maintenance teams, and I unfortunately...

`ASGI_THREADS` is the max number of simultaneous sync operations you can run; it's not related to simultaneous connections directly, but if all your connections are trying to do sync things...

Daphne only ever launches a single process; are you seeing processes or OS-level threads? Daphne only ever launches what you specify in `ASGI_THREADS` as the number of threads via a...

@umgelurgel If you are using Channels 2 then the scaling just works like any other Python server. Channels 1 you can still do but you'll need to run daphne and...

I had always envisaged the scope as something that was just opaquely passed down through each layer - the schema says what keys you can expect to find in it,...

Or yes, as you suggest @tomchristie, maybe we just say "pick a single key that is very unlikely to be the same name as a HTTP feature" and that's then...

So, I've definitely pondered this in the past, but it kind of conflates what an ASGI server _is_. Specifically, I would put forward that background tasks must always be secondary...

Right - we really discourage "background tasks" as a general concept within ASGI servers, as there's no execution guarantees or proper queuing/backpressure. The only thing I would want to encourage...

I personally don't think there's value in that, since task scheduling is an area that has such a broad scope of types of scheduling and guarantees that anything we add...

I wouldn't say that there shouldn't be _any_ work, but I feel comfortable saying there is no _guarantee_ that any code after the request body is closed will be executed...