Right, what James says here is pretty much my thoughts; it has been designed from the ground up not to be tied to Django, up to and including the fact that it's in separate packages; all the Django-specific stuff is in the "channels" package, while daphne, asgi_redis, asgiref etc. are useable by anything (I need to look into getting another framework like Flask working on top of it as a proof of concept).
My main sticking point is the design of the ASGI messaging interface, as that will be the one thing that everyone has to write against - are the number of calls we have enough? Does async support fit in alright? etc. The message formats themselves would work on anything that looks remotely similar. Andrew On Mon, Mar 13, 2017 at 5:17 AM, James Bennett <[email protected]> wrote: > 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 [email protected]. > To post to this group, send email to [email protected]. > 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-xJtxSJ4WyQHdHRacrda9XwQcc8h6FN > Kr-K_B_kOSK%3Dg%40mail.gmail.com > <https://groups.google.com/d/msgid/django-developers/CAL13Cg-xJtxSJ4WyQHdHRacrda9XwQcc8h6FNKr-K_B_kOSK%3Dg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. To post to this group, send email to [email protected]. 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/CAFwN1ur01RHWbHS9aR7OQFkBqLktSeOuZwC_gYuqbroWQGii2g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
