TimelyDataflow / TimelyDataflow/timely-dataflow
Consider a robust TCP / etc communication fabric
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 293
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 4
Description
Right now the "most distributed" communication fabric is a TCP-based fabric that doesn't think too hard about complicated things like data corruption or disconnects. The communication crate is meant to be designed in a way that allows folks to drop in their own communicator implementation, but it seems like one that could be generally useful is one that hardens the TCP based framework with things like CRCs, buffering and retransmission, reconnection if disconnection occurs; stuff like that.
Contributor guide
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 by reading the communication crate and its existing TCP-based fabric to understand how custom communicator implementations fit in. Clarify the scope and expected behavior for data corruption, buffering, retransmission, and reconnection before attempting the work; completion requires an agreed robust communication fabric covering the selected concerns.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- distributed-systems, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100