Sorry for the late response. This fell through the cracks. It's fine to have a read and a write active at the same time. It's only problematic to multiple reads or multiple writes at the same time.
On Sunday, March 13, 2022 at 2:06:36 PM UTC-7 Trending Now wrote: > Any update please ? > > Le samedi 12 mars 2022 à 11:55:28 UTC+1, Trending Now a écrit : > >> Hello >> >> Any update please. >> sorry, it's blocking for me :( >> >> Thank you very much ! >> >> Le vendredi 11 mars 2022 à 19:17:04 UTC+1, Trending Now a écrit : >> >>> Hello, >>> >>> I'm coding a bidirectional rpc using grpc. I'm using the asynchronous >>> API. >>> >>> The idea is to write the msg to the grpc::ClientAsyncReaderWriter< W, R >>> > stream and then call the Read in while loop till getting a false >>> status >>> >>> If I write to the stream, the program will simply crash. The reason is >>> the asynchronous API allows only “1 outstanding asynchronous write on the >>> same side of the same stream without waiting for the completion queue >>> notification“. >>> >>> Is there a way to force/prioritize the write operation after making a >>> read operation ? >>> >>> Thank you very much >>> >> -- 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 grpc-io+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/1aef2cfe-6729-4129-b0bb-440d7e4c05d5n%40googlegroups.com.
