Remove BlockingChannel and related classes
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 298
- Avg merge
- 21h 43m
- Merged PRs (30d)
- 9
Description
Once ambry moves completely to using the `Selector`, we can get rid of `BlockingChannel` and all the helper classes and interfaces (e.g. the `ConnectionPool` interface).
This issue can be addressed once #432 and #433 are closed.
Contributor guide
No contributing guide indexed for this repository
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 issues #432 and #433, which this cleanup depends on. Then locate BlockingChannel, its related helper classes and interfaces such as ConnectionPool, and inspect their remaining usages. Done means the Selector migration is complete and these obsolete classes and interfaces can be removed without remaining references.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems, networking
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100