diff options
| author | Juan Pedro Fisanotti <fisadev@gmail.com> | 2020-08-20 04:06:50 -0300 |
|---|---|---|
| committer | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2020-08-20 09:08:19 +0200 |
| commit | af190bf263f9cf584b6958fdc2a8d57e54926720 (patch) | |
| tree | d83e9d88d953ffa80cda3f570764e48387412853 | |
| parent | 26ccc7701daa77c72f467fdad9fedd0165531875 (diff) | |
[3.1.x] Improved wording in async views docs.
Backport of 41725602afebe2ddb018b99afe134384cc3bf69e from master
| -rw-r--r-- | docs/topics/async.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/topics/async.txt b/docs/topics/async.txt index 978d383308..528764ab2a 100644 --- a/docs/topics/async.txt +++ b/docs/topics/async.txt @@ -41,7 +41,7 @@ class-based view, this means making its ``__call__()`` method an ``async def`` to ``asyncio.coroutines._is_coroutine`` so this function returns ``True``. Under a WSGI server, async views will run in their own, one-off event loop. -This means you can use async features, like parallel async HTTP requests, +This means you can use async features, like concurrent async HTTP requests, without any issues, but you will not get the benefits of an async stack. The main benefits are the ability to service hundreds of connections without @@ -65,7 +65,7 @@ If you want to use these, you will need to deploy Django using messages about *"Synchronous middleware ... adapted"*. In both ASGI and WSGI mode, you can still safely use asynchronous support to -run code in parallel rather than serially. This is especially handy when +run code concurrently rather than serially. This is especially handy when dealing with external APIs or data stores. If you want to call a part of Django that is still synchronous, like the ORM, |