Mistakes in StreamingCalls.
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 4.4k
- Forks
- 627
- Avg merge
- 3d 15m
- Merged PRs (30d)
- 20
Description
I have some problems when using wire in android.
The prototype of my rpc is "single request" and "stream response", just like:
rpc doSomething (XXXXrequest) returns (stream XXXXResponse)
But wire converted this rpc call into "Pair<SendChannel, ReceiveChannel>" in Kotlin,
which seems to be a bi-direction streaming call, and my server returns an "502" status code.
Is there any solution? Thanks a lot!
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 source files, tests, repository reproduction, or Wire version. Start by reproducing the Kotlin output for an RPC with a single request and streaming response, then compare the generated call shape with the server's expected semantics. Done means the generated API uses the correct single-request/stream-response pattern and the server no longer returns 502.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, grpc, kotlin
- Domain
- api, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100