I'm trying to evaluate these two Websockets solutions for Django. Has anyone here done compared these?
I don't fully understand what the differences between them are. I think the main difference is that Channels can generalize all requests (websocket or request/response) to be handled by channel consumers, but if that's the case, then: 1. I think you only get that if you have all your traffic come through ASGI (Daphne), right? If you route WSGI traffic and Websockets traffic separately, then wouldn't you really have something similar to the solution described here: http://django-websocket-redis.readthedocs.io/en/latest/running.html#django-with-websockets-for-redis-behind-nginx-using-uwsgi. Or is there still some big difference between that solution and Channels? 2. If #1 above is the main difference, I don't fully understand what the advantage(s) of this are. Is the ASGI-only mode required in order to have the websockets code and the wsgi code share the Django session? Thanks! -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/12df27d1-2edd-42db-9e5f-ba393dfa07f0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
