Remove old note

This commit is contained in:
Andrew Godwin 2015-12-18 21:34:47 +00:00
parent 76ca034e63
commit ecb2e4c22b

View File

@ -4,8 +4,7 @@ Integration Notes
Django Channels is intended to be merged into Django itself; these are the Django Channels is intended to be merged into Django itself; these are the
planned changes the codebase will need to undertake in that transition. planned changes the codebase will need to undertake in that transition.
* The ``channels`` package will become ``django.channels``. The expected way * The ``channels`` package will become ``django.channels``, and main objects will keep their import path.
of interacting with the system will be via the ``Channel`` object,
* Obviously, the monkeypatches in ``channels.hacks`` will be replaced by * Obviously, the monkeypatches in ``channels.hacks`` will be replaced by
placing methods onto the objects themselves. The ``request`` and ``response`` 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 * The mismatch between signals (broadcast) and channels (single-worker) means
we should probably leave patching signals into channels for the end developer. we should probably leave patching signals into channels for the end developer.
This would also ensure the speedup improvements for empty signals keep working. 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.