Yes, this is the expected behavior. When the server sends the completion it then forgets about the RPC, while the client side has a more ownership relationship so keeps track of the RPC until it is fully closed.
On Wed, Jul 10, 2024 at 9:09 PM Steven Hu <[email protected]> wrote: > Hello gRPC community, > > I noticed some asymmetry for bidirectional RPC stream closure between RPC > client and RPC server. > > - If RPC stream client sends onCompleted(), server end will receive > onCompleted(). It closes the stream on client->server direction. server > could still send message to client. > - If RPC stream server sends onCompleted(), client end will receive > onCompleted(). *However, client end could no longer send messages to > server*. It seems that the entire stream has been closed. > > Is this expected? > > -- > 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/4c4123fa-2d31-48ef-9417-beb42c3a9adbn%40googlegroups.com > <https://groups.google.com/d/msgid/grpc-io/4c4123fa-2d31-48ef-9417-beb42c3a9adbn%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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/CANuT3qX55fOcg-L_BNKCLD5AmYHM5ivC35A8RKWXdEZGLokOLg%40mail.gmail.com.
