> I note that your examples do not include "receiving messages from a WebSocket and sending replies" - I would love to see how you propose to tackle this given your current API, and I think it's the missing piece of what I understand.
I've just added an `echo` WebSocket example. I've also now added support for broadcast, currently implemented using Redis Pub/Sub. There's a full example for a chat server that can be properly distributed. (*) Aside: Right now that *happens* to be implemented as middleware, but there's no reason it couldn't equally well be integrated at the server level, so not a detail to get sidetracked by. More important is how the application interface for it looks. (*) Yes, you'd have sticky WebSockets. -- 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/2da48b17-b47f-42e3-b1bb-4a0e5a9b5709%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
