On Thu, Dec 1, 2016 at 1:03 PM, Hank Sims <hanks...@gmail.com> wrote:
> You set it in the channel layer configuration in Django, like this:
> 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 already get this - trying to send to an outbound channel when it is
full will raise the ChannelFull exception. What you're seeing is the
inbound channel filling up, and the ASGI spec says that websocket protocol
servers should drop the connection if they can't send an incoming message
from a socket.
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 post to this group, send email to firstname.lastname@example.org.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout.