mirror of
https://github.com/django/daphne.git
synced 2025-05-01 22:23:45 +03:00
25 lines
1.0 KiB
ReStructuredText
25 lines
1.0 KiB
ReStructuredText
Integration Notes
|
|
=================
|
|
|
|
Django Channels is intended to be merged into Django itself; these are the
|
|
planned changes the codebase will need to undertake in that transition.
|
|
|
|
* The ``channels`` package will become ``django.channels``. The expected way
|
|
of interacting with the system will be via the ``Channel`` object,
|
|
|
|
* Obviously, the monkeypatches in ``channels.hacks`` will be replaced by
|
|
placing methods onto the objects themselves. The ``request`` and ``response``
|
|
modules will thus no longer exist separately.
|
|
|
|
Things to ponder
|
|
----------------
|
|
|
|
* The mismatch between signals (broadcast) and channels (single-worker) means
|
|
we should probably leave patching signals into channels for the end developer.
|
|
This would also ensure the speedup improvements for empty signals keep working.
|
|
|
|
* It's likely that the decorator-based approach of consumer registration will
|
|
mean extending Django's auto-module-loading beyond ``models`` and
|
|
``admin`` app modules to include ``views`` and ``consumers``. There may be
|
|
a better unified approach to this.
|