Andrew Godwin
Andrew Godwin
Documenting this in the README is the correct approach I feel. I don't think there's any other sensible way around this without throwing away the significant efficiency gains of reading...
No, the backpressure is valuable to stop Redis filling up, and I think that part still works fine if it's shared across channels.
Yes, let's get this in once it's possible with the backport. The decorators have always been very annoying when typing is involved!
I don't think so, I'd love someone else to take on mypy stuff rather than having to stare at it for hours!
Agreed, this seems like a sensible feature that's needed above and beyond the channel layer statistics interface. I've been a fan of the e.g. HaProxy stats info for a while.
Well, the main question is if it should be on the Daphne instance directly on a separate path/port, which is probably easiest to implement and scale but harder to aggregate,...
My problem with having it come over the channel layer is, how do you identify the hosts? This is a problem we faced setting up monitoring at work for some...
Yes, I'm not tying into something that tightly. This is why I think a HTTP endpoint on Daphne itself makes the most sense for the short term - it's already...
No progress has been made partially because Daphne has been heavily rewritten for the upcoming 2.0 release as the way applications have run has changed substantially. HTTP/WebSocket handling is done...
Those should work for asgi_redis, yes, we used them at work for a little while.