derhuerst/lossy-state-sync-stream

re-transmit chunks if no ack received

Open

#2 opened on May 30, 2020

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (0 forks)github user discovery
enhancementhelp wanted

Repository metrics

Stars
 (1 star)
PR merge metrics
 (No merged PRs in 30d)

Description

This will give lossy-state-sync-stream TCP-like properties, guaranteeing (eventual) sync of the state.

We reduce the lower limit on the retransmission timeout to be 50 ms instead of one second. SSH runs over TCP and rarely benefits from fast re- transmissions, meaning it generally cannot detect a dropped keystroke in less than a second.

Contributor guide

Research direction
Implement a retransmission mechanism: when a chunk is sent, start a timer. If no acknowledgment is received within the timeout, resend the chunk and reset the timer. Use a buffer of unacknowledged chunks. Consider using a dynamic timeout based on round trip time estimates.
Tech stack
javascript
Domain
backendstream processing
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.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
JavaScriptNode.js Streams
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40