onepub-dev / onepub-dev/reVault
look to using http.rs for the key exchange server.
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 4
- Forks
- 0
- Avg merge
- 1h 55m
- Merged PRs (30d)
- 1
Description
We shouldn't use our own http parsing, client or server so replace it with standard rust libraries where possible.
look at using tower create rather than our own rate limiter logic if it makes sense to do so.
where we copy &[u8] to /from strings look to use the hec crate.
looks like our sub commands for the cli are not using clap. Ensure that we use clap consistently through the code base.
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 surveying the codebase for the custom HTTP parsing, client and server, rate limiter, byte/string conversions, and CLI subcommand handling described in the issue. Compare each area with the requested standard Rust libraries, tower, hec, and clap; done means the custom implementations are replaced where appropriate and CLI subcommands use clap consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, cli, networking
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100