mirror of
https://github.com/django/daphne.git
synced 2025-04-21 01:02:06 +03:00
Fixed minor typos in docs/. (#439)
* Fixed typo in docs/inshort.rst. * Fixed typo in docs/asgi.rst.
This commit is contained in:
parent
ce65de323c
commit
43b23dc295
|
@ -123,7 +123,7 @@ so that a querying client only sees some portion of the messages. Calling
|
|||
``receive`` on these channels does not guarantee that you will get the
|
||||
messages in order or that you will get anything if the channel is non-empty.
|
||||
|
||||
*Single-reader channel* names contain an question mark
|
||||
*Single-reader channel* names contain a question mark
|
||||
(``?``) character in order to indicate to the channel layer that it must make
|
||||
these channels appear globally consistent. The ``?`` is always preceded by
|
||||
the main channel name (e.g. ``http.response.body``) and followed by a
|
||||
|
|
|
@ -66,7 +66,7 @@ and WebSockets) and *worker servers* (ones that run your Django code) to
|
|||
fit your use case.
|
||||
|
||||
The ASGI spec allows a number of different *channel layers* to be plugged in
|
||||
between these two components, with difference performance characteristics, and
|
||||
between these two components, with different performance characteristics, and
|
||||
it's designed to allow both easy sharding as well as the ability to run
|
||||
separate clusters with their own protocol and worker servers.
|
||||
|
||||
|
|
Loading…
Reference in New Issue
Block a user