Josiah Kaviani

I read connected issue. Those mechanics suppose to do different thing. I'm fine to implement behavior described in this issue as a separate package. But I still want to hear...

Hi, I'm the author of an alternative [dependency](https://github.com/dry-python/dependencies) injector library (dependencies part of the [dry-python](https://github.com/dry-python) project). We already have [integration with Celery](https://dependencies.readthedocs.io/en/latest/contrib/celery/). We decide not to fight with Celery worker...

Actually, we use function-based and class-based tasks depending on the `bind` parameter in the scope of the Injector. https://github.com/dry-python/dependencies/blob/5fcc9313da03f28af2165aa9cb434aa333d0f1d9/src/dependencies/contrib/_celery.py#L55-L63

Hi, I'm the author of an alternative [dependency](https://github.com/dry-python/dependencies) injector library (dependencies part of the [dry-python](https://github.com/dry-python) project). We already have [integration with pytest suite](https://dependencies.readthedocs.io/en/latest/contrib/pytest/). We decide not to fight with pytest...

AFAIK nothing happens to solve #315?

Maybe its possible add buffer locals variables with some kind of request middlewares to solve this? Than it will be really simple to customize this behavior.

Hi @ivorbosloper, Probably you choose wrong place to hold a request. You shouldn't block channels worker with any kind of waiting process. Maybe my example can give you some inspiration....

My main concern about solution suggested by you, that you're trying to store state internally in the worker process. While Channels 1.0 is a synchronous solution all the way down...

I think channel layer is preferred solution. If it becomes full, daphne can send updated version of statistic data next time. So statistic will be lost only when we restart...

Consul telemetry integration seems the easiest way to me. But it too tight into vendor software. Not everyone​ will be happy with it.