gRPC: find a way for the single request / streaming response to do a blocking write
Open
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 4.4k
- Forks
- 627
- Avg merge
- 3d 15m
- Merged PRs (30d)
- 20
Description
doesn’t strictly need to be a duplex call
S, R, R , R, R
neither does this
S, S , S, S, R
this definitely does
S, R, S, R, S, R
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 mapping the three request/response sequences in the issue to the repository’s gRPC call and streaming entry points. Determine whether single-request or single-response streaming can support a blocking write without requiring a duplex call. Done means the supported call shapes and blocking behavior are defined clearly enough to implement and verify.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100