Lifespan
See original GitHub issueDoes daphne
currently (or plan to) support the lifespan protocol? We are working on ASGI support for Sanic and looking to make sure that it includes this feature.
Issue Analytics
- State:
- Created 4 years ago
- Comments:18 (9 by maintainers)
Top Results From Across the Web
Lifespan: Rhode Island Hospitals and Health Services
Lifespan Health System operates award-winning Rhode Island hospitals and provides health services at dozens of locations throughout the state.
Read more >Lifespan
Lifespan provides information, guidance and more than 30 services for older adults and caregivers. · We offer a variety of workshops each month!...
Read more >LifeSpan Fitness: Fitness Equipment for Home & Work
LifeSpan Fitness offers a variety of products to helps promote a healthy lifestyle while you work! Check out our Treadmills, Treadmill Desks, Bike...
Read more >LifeSpan: Home
LifeSpan connects families and communities by strengthening lives; since 1945. Programs include Elderly Services, financial counseling, Guardianship, more.
Read more >Home - Lifespan - Abilities IlluminatedLifespan - Abilities ...
LIFESPAN, Inc. is a non-profit 501 (c) 3 organization that provides services to infants six weeks of age to senior adults with disabilities....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Feels like a lifespan ago… 🥁
@ahopkins Thanks too!
I am still happy to take a PR adding this.
I am still maintaining Daphne, even if not super-actively. A release pulling in the recent PRs, and updating Twisted, and Python support is on the list for post-Django 4.1a1.
Aside (trying to communicate what’s going on):
I think there are two segments here. The full-on ASGI/async folks, who aren’t interested in Daphne much anyway, and the folks using Django/Channels for whom plenty are using Daphne very successfully.
The focus has entirely been on the core use cases around Channels, and on Django’s async support.
To that: Channels was updated to ASGI v3, and that went well, and Django 4.1 includes another batch of async improvements.
As far as I can tell that’s what we’re aiming for, and I can’t help but be positive about it, and think we’re on a good road.
All that time, Daphne has had my eye, and I’ve made releases where needed and merged what I’ve had time for, but it’s not been pressing (not compared to other bits in the stack).
It still works fine; that’s one of the benefits of building on twisted it turns out. The X-feature wasn’t added doesn’t mean more than it wasn’t essential yet.
I appreciate that if you’re in the wider async/ASGI world, Daphne isn’t as INSERT-YOUR-ADJECTIVE as the other servers… But for a moderately high-throughput websocket server for Channels it does perfectly well.
And as life returns to normal, I still hope to pick up the pace.
As well as working on Django, I do OSS in the Django-world for a hobby — always have. Channels &co is where that time will go for the next period — which means few years at least. (I can’t say more than that.)
If folks want to join in and help, then super. Equally, if you’re more of the I’ll just use X line, I’m all with you.
Hopefully that clarifies the status a little.