grpc / grpc/grpc-java

binder: CallStreamObserver request()s are not reflected by isReady() at the peer

Open
#9,010 1 comment 0 reactions 1 assignee Claimed by @jdcormie View on GitHub
binder enhancement
Dominant language
Java
Stars
12.1k
Forks
4k
Avg merge
2d 17h
Merged PRs (30d)
37

Description

### Is your feature request related to a problem?
Yes, lack of message-by-message stream flow control

### Describe the solution you'd like
The binder transport should implement the isReady() and request() methods of CallStreamObserver to behave as documented.

### Describe alternatives you've considered
Today, system designers needing flow control must include tokens / acks in their API as explicit messages.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.