diff options
| author | Adam Johnson <me@adamj.eu> | 2020-02-20 14:05:47 +0000 |
|---|---|---|
| committer | Carlton Gibson <carlton.gibson@noumenal.es> | 2020-02-20 15:06:37 +0100 |
| commit | 80e6639e22be464cc8b042450f505293a617967a (patch) | |
| tree | 71c34a1ad4c9238129f99f10d8b7652aeaf7d6e0 | |
| parent | a73489f162003472708887fac9b98987af6464fd (diff) | |
[3.0.x] Fixed #31182 -- Adjusted release notes for ASGI support.
Backport of a6b3938afc0204093b5356ade2be30b461a698c5 from master
| -rw-r--r-- | docs/releases/3.0.txt | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/docs/releases/3.0.txt b/docs/releases/3.0.txt index 50c98ade58..51ca584ecb 100644 --- a/docs/releases/3.0.txt +++ b/docs/releases/3.0.txt @@ -54,6 +54,11 @@ This is in addition to our existing WSGI support. Django intends to support both for the foreseeable future. Async features will only be available to applications that run under ASGI, however. +At this stage async support only applies to the outer ASGI application. +Internally everything remains synchronous. Asynchronous middleware, views, etc. +are not yet supported. You can, however, use ASGI middleware around Django's +application, allowing you to combine Django with other ASGI frameworks. + There is no need to switch your applications over unless you want to start experimenting with asynchronous code, but we have :doc:`documentation on deploying with ASGI </howto/deployment/asgi/index>` if |