Correct, if it's a server-streaming RPC or bi-directional streaming RPC, the server would send multiple response messages on the same http2 stream. The server will send END_OF_STREAM in the trailers after the last message it would send. If it is a unary RPC or client-streaming RPC, the server will only send one response message.
On Thursday, September 12, 2019 at 12:59:24 PM UTC-7, Yaxiong Zhao wrote: > > On https://github.com/grpc/grpc/blob/master/doc/PROTOCOL-HTTP2.md > it was mentioned that response End of stream is marked by: > For responses end-of-stream is indicated by the presence of the END_STREAM > flag on the last received HEADERS frame that carries Trailers. > > Does gRPC sends multiple such responses on the same HTTP2 stream id? > > I was tracing the network traffic, and decode grpc message on the wire. > > I thought gRPC never send multiple response on the same stream ID. But > found that it indeed do that in some cases. > -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/607e5d8c-ccce-4831-9e95-6024fd275ba0%40googlegroups.com.
