On Saturday, May 30, 2015 at 10:40:26 PM UTC+1, Emil Stenström wrote: > > Client A clicks a button on the site, that sends an normal ajax request to > Django. In the view a message is passed from Django to the SSE process. >
How, you still need some kind of interprocess communication So the SSE process is VERY simple. It just connects to clients and passes > on messages the all clients connected. > VERY simple is an oversimplification in my opinion. I also do not see any reason for supporting it inside Django currently when things like autobahn.ws exist, the only thing missing there is the communication between the processes. I am not sure what people are expecting here from Django (and from your explanations I am still not really convinced or see a usecase at all). Since the message passing between the server processes should be language/framework agnostic anyways, this would be better suited for a third party project anyways. Reimplementing one of the existing SSE/Websockets implementations does not really seem like a win to me either. Cheers, Florian -- 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 http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/86b8ff28-b35f-49cd-8e95-30ace07c9d51%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
