Data Exchange: Flow Control
Open
- Dominant language
- Go
- Stars
- 11
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Building on the raw data exchange issue, we can start to control the data flow. This requires CHOKE and UNCHOKE.
The python reference implementation seems to use LEDBAT here, we could start with something simple and iterate towards a more sophisticated solution.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the existing raw data exchange implementation and the Python reference implementation's LEDBAT flow-control behavior. Read the flow-control requirements in RFC 7574 and determine how CHOKE and UNCHOKE fit the current exchange. Done means the Go implementation supports these messages with a defined, testable flow-control behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100