This not only meant that all request data had to be re-serialized over the network, but that you needed to deploy and scale two separate sets of servers. Channels 2 changes this by running the Django code in-process via a threadpool, meaning that the network termination and application logic are combined, like WSGI.
<https://www.besanttechnologies.com/training-courses/data-warehousing-training/datascience-training-institute-in-chennai> Data Science Training in Chennai <https://www.besanttechnologies.com/training-courses/data-warehousing-training/datascience-training-institute-in-chennai> Data Science Training in Bangalore <https://www.besanttechnologies.com/training-courses/data-science-training-in-bangalore> -- 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/d2c53ad1-1312-49e6-975b-2f4f966525d2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
