Re: Channels, Websockets and 'Backpressure'

> > 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

Re: Channels, Websockets and 'Backpressure'

Thanks, Andrew. A few follow-up questions: 1. How would one go about increasing the default maximum queue size? I saw some reference to this when I was researching the problem yesterday, but I couldn't find the setting that would change it. 2. Shouldn't there be a way to resolve the backpressu

Re: Figuring out what has changed at save()

For what it's worth, I can imagine on way of doing this. I could use signals to monkeypatch the instance at post_init, adding an attribute called "post_init_status." Then I could compare this value with "status" at post_save. Please save me from doing something so ugly. On Mar 6, 12:28 am, Rama

Re: Figuring out what has changed at save()

Rama: Thanks, but that's no good. That would trigger the action whether or not the post is saved as "draft." Hank Sims On Mar 6, 12:28 am, Rama Vadakattu wrote: > So you need to trigger an action the first time you save an object in > to the database. > > ---

GeoDjango Lookup Woes

typical shell session. The first error listed is an IPython error -- I don't think that's it, because it fails the same way in the plain Python shell, but I'll leave it here in case I'm missing something. Probably I'm doing something extremely boneheaded. Any ideas?