clj-commons / clj-commons/aleph
Add options for custom thread pool names
Nobody has claimed this yet.
- Dominant language
- Clojure
- Stars
- 2.6k
- Forks
- 242
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 1
Description
# Problem
Currently, thread pool names are hardcoded ([server](https://github.com/clj-commons/aleph/blob/2affe039156938a52c4fdf56fd5ae2b660c5f109/src/aleph/netty.clj#L1731) and [client](https://github.com/clj-commons/aleph/blob/2affe039156938a52c4fdf56fd5ae2b660c5f109/src/aleph/netty.clj#L1287)). This means that their threads they cannot be easily differentiated when multiple pools of the same type are instantiated in the same process.
# Solution
Add options for passing in a custom thread pool name.
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 in src/aleph/netty.clj at the server thread-pool code near line 1731 and client code near line 1287. Trace how options reach these pools and inspect nearby tests or usage examples. Done means both server and client support custom thread-pool names while retaining the current defaults.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- backend, networking
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 58/100