grpc / grpc/grpc-java

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

Abierto
#9,010 1 comentario 0 reacciones 1 asignado Reclamado por @jdcormie Ver en GitHub
binder enhancement
Lenguaje dominante
Java
Estrellas
12.1k
Forks
4k
Merge medio
2 d 17 h
PR fusionados (30 d)
37

Descripción

### 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.

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.