tornadoweb / tornadoweb/tornado
Max server connections
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 22.2k
- Forks
- 5.6k
- Avg merge
- 3h 42m
- Merged PRs (30d)
- 16
Description
Do tornado HTTPServers support the notion of max connections? In my use case, I would like the server to stop taking connections once we hit some limit (say 100 users). Then resume once connections drop out.
Barring this, is there a recommended way to know how many connections currently exist? I can add a counter to the RequestHandlers but am wondering if there's a canonical method.
Thank you!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing Tornado's HTTPServer connection handling and the existing server documentation or API entry points. Determine whether a maximum connection limit or canonical active-connection count is supported, then define the expected behavior when the limit is reached and connections later close.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100