Unify API
Open
- Dominant language
- Rust
- Stars
- 172
- Forks
- 49
- PR merge metrics
- No merged PRs in 30d
Description
In the [async-native-tls](https://github.com/async-email/async-native-tls), there is a single TlsStream, but in this crate, there are two different Stream implementation. It would be nice if we have unified API that can support different engine.
Contributor guide
No contributing guide indexed for this repository
Research direction
Compare this crate's two Stream implementations with the single TlsStream in async-native-tls, starting from the public stream API entry points. Determine how one API could support different engines and define the compatibility expectations. Done means the crate exposes a unified Stream API without losing support for the existing engines.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking, security
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100