WSGI is a framework-independent protocol to allow HTTP servers to communicate with Python applications. It defines a standard API and serialization mechanism to be used by the HTTP server and the Python application in order to allow them to work together.
WSGI *only* does plain HTTP. And in fact it only does plain HTTP/1.1. It cannot handle quite a few features of HTTP/2, and provides no support whatsoever for modern bidirectional web protocols like WebSocket. ASGI attempts to fill that gap by defining a protocol which allows these other protocols/features to communicate with Python applications. In much the same way as WSGI, it defines an API and serialization. There is nothing Django-specific about ASGI. ASGI is not coupled to Django. ASGI is just a necessary precondition for being able to build the kinds of things in Django that Channels aims to provide, in much the same way that WSGI -- or something like it -- is a necessary precondition for current request/response HTTP/1.1 Django to exist. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAL13Cg-xJtxSJ4WyQHdHRacrda9XwQcc8h6FNKr-K_B_kOSK%3Dg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
