stackabletech/tokio-zookeeper

Support non-TCP connections and handshakes

Open

#8 opened on Jul 29, 2018

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Rust (22 forks)auto 404
help wanted

Repository metrics

Stars
 (77 stars)
PR merge metrics
 (PR metrics pending)

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

Research direction
Start by reading the source code for `Packetizer` and `ZooKeeper` to understand how TCP connections are currently handled. Examine the `ZooKeeperTransport` trait and see how it abstracts the transport. Then plan how to move the connection setup and handshake into `Packetizer::new` so it can support non TCP transports.
Tech stack
rust
Domain
networkingdistributed systems
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustAsync/awaitGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55