TimelyDataflow / TimelyDataflow/timely-dataflow
A Question About Asynchrony
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 293
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 4
Description
How are async operations handled?
If a message to a vertex represents a request for an HTTP Request, which causes another messages to be emitted with the returned payload, how would that fit into this model?
I may be misreading things but I don't see how an async operation and the processing of a message that doesn't output in messages can be told apart.
Are async operations exclusively intended to be "outside" the system?
(Admittedly I'm new to rust and may just be misunderstanding things).
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
No source files, tests, or entry points are named. Start by tracing how messages with no downstream output and asynchronous request/response behavior are represented, then clarify whether async operations belong inside or outside the dataflow system; done means the expected model and behavior are explicitly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100