temporalio / temporalio/temporal
Consider adding an option for bidirectional gRPC streaming instead of unary RPC
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Is your feature request related to a problem? Please describe.
Some traffic management solutions or connection policies may benefit from having flexibility here
Describe the solution you'd like
Ideally an option to use gRPC bidirectional streaming for sending / receiving multiple requests rather than using long polling with unary RPC
Describe alternatives you've considered
An alternative would be to shift entirely to streaming, but flexibility would be nice to have.
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
The issue names no files, tests, or entry points. Start by locating the existing unary gRPC long-polling path and its request/response APIs, then determine the scope of an optional bidirectional-streaming mode. Done would require an agreed design and support for both modes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, grpc
- Domain
- api, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100