websockets-rs / websockets-rs/rust-websocket
Extract core features to independent sub-crates
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.6k
- Forks
- 225
- PR merge metrics
- No merged PRs in 30d
Description
Currently, rust-websocket provides the all features from a single crate, but in the case of using only certain features (like encoding/decoding data frames) most of these features are unneeded.
It is desirable to extract some components which do not depend on the higher level implementations (such as client and server) as independent crates.
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 mapping the current single-crate components and their dependencies, especially frame encoding and decoding versus client and server implementations. Determine which lower-level components can stand alone without higher-level dependencies. Done means the selected core features are available as independent crates while the existing functionality remains usable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100