Lifespan question
- Dominant language
- No language data
- Stars
- 3.6k
- Forks
- 147
- Avg merge
- 5m
- Merged PRs (30d)
- 1
Description
Hey, First of all thanks for this initiative, it's great!
I have a question regarding the lifespan to manage objects.
Let's say that I would like to provide realtime data, and I have an object that subscribes via ws and keeps certain data updated, so I can expose a route to provide this data aggregated. Should I create the object with the lifespan approach? Or which is your recommendation?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the issue body and clarify the intended lifespan behavior for an object that subscribes via WebSocket and exposes aggregated data through a route. Done means recording a clear recommendation or usage guidance that directly answers the question.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fastapi
- Domain
- backend
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100