Usage of channel layer should not be limited on Django only according to the document.
Channel layers allow you to talk between different instances of an application.
Although I understand that Channel Layer is a sub product for Channels, is it possible to provide a pure Channel Layer such that Django is not a dependencies?
For example, I would like to write a python application with the same Channel Layer's implementation (channel-redis to be specific) for interacting redis. But, I don't want Django to be a dependency of that python application.
I have read some source codes for understanding the relationship between Channel Layer & Django. It seems the only connection between them is channels.layers.get_channel_layer. Literally, it read Django settings, and instantiate the corresponding Channel Layer with those settings. It seems we can get rid of the django import statement if we simply take out channels.layers.get_channel_layer from layers.py. Is it true?
Usage of channel layer should not be limited on Django only according to the document.
Although I understand that Channel Layer is a sub product for Channels, is it possible to provide a pure Channel Layer such that Django is not a dependencies?
For example, I would like to write a python application with the same Channel Layer's implementation (channel-redis to be specific) for interacting redis. But, I don't want Django to be a dependency of that python application.
I have read some source codes for understanding the relationship between Channel Layer & Django. It seems the only connection between them is
channels.layers.get_channel_layer. Literally, it read Django settings, and instantiate the corresponding Channel Layer with those settings. It seems we can get rid of the django import statement if we simply take outchannels.layers.get_channel_layerfromlayers.py. Is it true?