mirror of
https://github.com/django/daphne.git
synced 2025-04-21 01:02:06 +03:00
Remove old note
This commit is contained in:
parent
76ca034e63
commit
ecb2e4c22b
|
@ -4,8 +4,7 @@ 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,
|
||||
* The ``channels`` package will become ``django.channels``, and main objects will keep their import path.
|
||||
|
||||
* Obviously, the monkeypatches in ``channels.hacks`` will be replaced by
|
||||
placing methods onto the objects themselves. The ``request`` and ``response``
|
||||
|
@ -17,8 +16,3 @@ 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.
|
||||
|
|
Loading…
Reference in New Issue
Block a user