> > You set it in the channel layer configuration in Django, like this: > https://github.com/django/asgi_redis/#usage >
Ah, thank you. Sorry I missed that. > How would you propose this worked? The only alternative to closing the > socket is to buffer the messages in memory and retry sending them, at which > point you might have the case where the client thinks they have a working > connection but it's not actually delivered anything for 30 seconds. Hard > failure is preferable in distributed systems in my experience; trying to > solve the problem with soft failure and retry just makes problems even more > difficult to detect and debug. > I guess the "hard failure" I would prefer in this case -- though maybe not all cases -- is simply discarding new outbound messages when their queue is full. Or else some sort of mechanism from within my consumers.py that would allow me to forgo writing to a channel if its queue is full. -- 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 post to this group, send email to [email protected]. 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/CA%2BD3Ovis1T0jDD_d7kwS3ZA1EmGeG5bPqoME7kT6%2BsBdG3aicA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
