> On 06 May 2016, at 21:56, Donald Stufft <don...@stufft.io> wrote: > >> On May 6, 2016, at 3:49 PM, Aymeric Augustin >> <aymeric.augus...@polytechnique.org >> <mailto:aymeric.augus...@polytechnique.org>> wrote: >> >> Sure, this works for WSGI, but barring significant changes to Django, it >> doesn’t make it convenient to handle WSGI synchronously and WebSockets >> asynchronously with the same code base, let alone in the same process. > > User level code would not be handling WebSockets asynchronously, that would > be left up to the web server (which would call the user level code using > deferToThread each time a websocket frame comes in). Basically similar to > what’s happening now, except instead of using the network and a queue to > allow calling sync user code from an async process, you just use the > primitives provided by the async framework.
Ah, right! I think this would be quite similar to a synchronous, in-memory channels backends. -- Aymeric. -- 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/EA79C789-E486-4073-8961-06E1F350F405%40polytechnique.org. For more options, visit https://groups.google.com/d/optout.
