Context Navigation

Changes between Initial Version and Version 1 of Ticket #33699, comment 9

-              initial
+              v1
 See [https://github.com/django/asgiref/issues/66 this long discussion on the asgiref repo] for more context.
 Disconnect handling requires consuming the request body messages from the receive queue.
+Disconnect handling requires consuming the request body messages from the receive queue, so that the disconnect message (if sent) is available.
 If the ASGI could pass an open file descriptor for the request body to the application, then in principle we could use that directly, rather than needing to spool the body file (to memory or disk, depending on size). That would loose the ability to have the server and application on different servers, but that might be OK in many cases. (IDK)
+If the ASGI server (Daphne/Uvicorn/Hypercorn/...) could pass an open file descriptor for the request body to the application (Django), then in principle we could use that directly, rather than needing to spool the body file (to memory or disk, depending on size). That would loose the ability to have the server and application on different servers, but that might be OK in many cases. (IDK)
 That would need first the PoC, and then the spec change (or clarification, if you prefer) to go with it.