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

Update inshort a little.

Browse Source
This commit is contained in:
Andrew Godwin 2016-02-28 22:10:02 -08:00
parent cdde27b55a
commit 00dd9615ff
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/inshort.rst
View File

@ -11,6 +11,8 @@ that allows two important features:
* WebSocket handling, in a way very :ref:`similar to normal views <websocket-example>` * WebSocket handling, in a way very :ref:`similar to normal views <websocket-example>`
* Background tasks, running in the same servers as the rest of Django * Background tasks, running in the same servers as the rest of Django
It allows other things too, but these are the ones you'll use to start with.
How? How?
---- ----
@ -36,7 +38,7 @@ change from running Django under a WSGI server, to running:
* An ASGI server, probably `Daphne <http://github.com/andrewgodwin/daphne/>`_ * An ASGI server, probably `Daphne <http://github.com/andrewgodwin/daphne/>`_
* Django worker servers, using ``manage.py runworker`` * Django worker servers, using ``manage.py runworker``
* Something to route ASGI requests over, like Redis or a database. * Something to route ASGI requests over, like Redis.
What else does Channels give me? What else does Channels give me?
@ -74,7 +76,7 @@ and high throughput over guaranteed delivery, which doesn't match some
message queue designs. message queue designs.
Some features, like :ref:`guaranteed ordering of messages <enforcing-ordering>`, Some features, like :ref:`guaranteed ordering of messages <enforcing-ordering>`,
are opt-in as they incur a performance hit. are opt-in as they incur a performance hit, but make it more message queue like.
Do I need to worry about making all my code async-friendly? Do I need to worry about making all my code async-friendly?