django/daphne
1
1
Fork 0
mirror of https://github.com/django/daphne.git synced 2025-04-21 17:22:03 +03:00
Code Issues Packages Projects Releases Wiki Activity

Changed three "these/those" into explicit names

Browse Source 
The original version was unclear to me. It sounded like Go channels were the ones that are network-transparent even though we mean to say that Django's are.

So I simply removed these/those and used "Go channels" and "Django channels" explicitly. (But *do* check whether I got it right! :-) )
This commit is contained in:
Reinout van Rees 2015-12-14 14:26:37 +01:00
parent aa3f834e3a
commit ff45689c46
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
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
difference is that these channels are network-transparent; the implementations
If you've used `channels in Go <https://gobyexample.com/channels>`_: Go channels
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
and producers running in different processes or on different machines.