django/daphne
1
1
Fork 0
mirror of https://github.com/django/daphne.git synced 2025-07-18 03:42:18 +03:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #42 from reinout/patch-1

Browse Source 
Changed three "these/those" into explicit names
This commit is contained in:
Andrew Godwin 2015-12-14 09:26:43 -08:00
commit b2ba048b9e
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/concepts.rst
View File

@ -46,8 +46,9 @@ The channels have capacity, so a load of producers can write lots of messages
into a channel with no consumers and then a consumer can come along later and into a channel with no consumers and then a consumer can come along later and
will start getting served those queued messages. will start getting served those queued messages.
If you've used `channels in Go <https://gobyexample.com/channels>`_, these are reasonably similar to those. The key If you've used `channels in Go <https://gobyexample.com/channels>`_: Go channels
difference is that these channels are network-transparent; the implementations are reasonably similar to Django ones. The key difference is that
Django channels channels are network-transparent; the implementations
of channels we provide are all accessible across a network to consumers of channels we provide are all accessible across a network to consumers
and producers running in different processes or on different machines. and producers running in different processes or on different machines.