mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2024-12-23 01:25:58 +00:00
Code Issues 25 Releases Wiki Activity

Improved wording in async views docs.

Browse Source
This commit is contained in:
Juan Pedro Fisanotti 2020-08-20 04:06:50 -03:00 committed by GitHub
parent e2013b260a
commit 41725602af
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/topics/async.txt
View File

@ -39,7 +39,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
@ -63,7 +63,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,