shell-pool / shell-pool/shpool
support simultanious client connections
Open
Nobody has claimed this yet.
big
enhancement
- Dominant language
- Rust
- Stars
- 2k
- Forks
- 67
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 15
Description
Several people have brought up this feature as a nice thing to have. This could actually be somewhat tricky given shpool's existing architecture because of the way we have a per-session lock.
We may want to have a notion of readwrite sessions and readonly sessions the same way that abduco does.
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 tracing shpool's per-session lock and how client connections are handled; no specific files or tests are named in the issue. Compare the architecture with abduco's readwrite and readonly session model, then define the behavior and implementation scope needed for simultaneous clients.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100