On Friday, 2 June 2017 13:04:48 UTC+10, Andrew Godwin wrote: > > You can't do what you ask with the current Groups system - it is > deliberately very simple as anything more complex involves picking scaling > tradeoffs that are particular to the thing it's powering. You'll have to > layer some of your own code on top of groups (you can keep groups for the > broadcast message bit, and then add state management for processes done in > the websocket connect/disconnect methods) >
I guess this means I need to do my own expiration processing too. Are there any examples you know of that I can look at for inspiration? I am surprised this sort of thing doesn't seem to have come up before. Thanks -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/1d699f5b-441b-455b-9828-2a18326b616f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
