On 05/06/2016 01:56 PM, Donald Stufft wrote: > 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.
I think (although I haven't looked at it carefully yet) you're basically describing the approach taken by hendrix [1]. I'd be curious, Andrew, if you considered a thread-based approach as an option and rejected it? It does seem like, purely on the accessibility front, it is perhaps even simpler than Channels (just in terms of how many services you need to deploy). Carl [1] http://hendrix.readthedocs.io/en/latest -- 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/572CFC63.9040308%40oddbird.net. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature
