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

Talk about URL routing/views in getting started (refs #92)

Browse Source
This commit is contained in:
Andrew Godwin 2017-01-23 10:13:11 -08:00
parent f4d38ef778
commit 891eaf0051
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/getting-started.rst
View File

@ -228,6 +228,13 @@ And what our routing should look like in ``routing.py``::
route("websocket.disconnect", ws_disconnect), route("websocket.disconnect", ws_disconnect),
] ]
Note that the ``http.request`` route is no longer present - if we leave it
out, then Django will route HTTP requests to the normal view system by default,
which is probably what you want. Even if you have a ``http.request`` route that
matches just a subset of paths or methods, the ones that don't match will still
fall through to the default handler, which passes it into URL routing and the
views.
With all that code, you now have a working set of a logic for a chat server. With all that code, you now have a working set of a logic for a chat server.
Test time! Run ``runserver``, open a browser and use that same JavaScript Test time! Run ``runserver``, open a browser and use that same JavaScript
code in the developer console as before:: code in the developer console as before::