stackabletech / stackabletech/tokio-zookeeper
Support non-TCP connections and handshakes
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 78
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
Packetizer is fully generic over the underlying transport. However, ZooKeeper is not (it requires tokio::net::TcpStream for connect). We should use the ZooKeeperTransport trait to bring all network connectivity things into Packetizer::new (including the handshake, which can then be reused for session re-establishment).
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 at ZooKeeper::connect and Packetizer::new, then read the ZooKeeperTransport trait and how the current TcpStream handshake is performed. Trace session re-establishment as well. Done means connectivity and handshake handling are supplied through Packetizer::new, support non-TCP transports, and allow the handshake to be reused during session re-establishment.
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
- 35/100