binder: CallStreamObserver request()s are not reflected by isReady() at the peer
Offen
binder
enhancement
- Vorherrschende Sprache
- Java
- Sterne
- 12.1k
- Forks
- 4k
- Ø Merge
- 2 T. 17 Std.
- Gemergte PRs (30 T.)
- 37
Beschreibung
### 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.
Beitragsleitfaden
Bewertung
Dieses Issue wurde noch nicht bewertet.