Don't you just have to send a message to an appropriate group which contains just that users/sessions connections/consumers and in the message handler on the consumer call 'self.close()' and remove the consumer from any subscriptions. If I understand the docs, in the disconnect method is still called so can do it there, and should be anyway. (Although it doesn't hurt to do it twice group_discard() is defined a s NOOP if the consumer's unique channel isn't in the group) Or have I missed something,? On Mon, 2020-04-06 at 03:08 -0700, krnrrr wrote: > or maybe any example of "superuser with groups: he can list all > connections and close them if he likes"-type of application. All i > found was some types of chats, but none of them included some kind of > "chat-admin" with management of the rooms and visitors > > > > -- > > 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 [email protected]. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/ad5f38cd-0d4e-4187-a2c2-d092df869f8e%40googlegroups.com > . >
-- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/530606d8f5e1320eed464ffe94e968b66260b0f0.camel%40gammascience.co.uk.
