Hi In GRPC Asynchronous Streaming , it is mentioned that we cannot do back to back write() on the same RPC Call and we can do next Write() only after getting back tag from completion queue.
Suppose if the application is multi threaded and if any given thread can do Write(), to synchronize between getting tag from CQ and allowing next Write(), we might need to use mechanism like signaling a thread which is waiting to do next Write() Operation. Is application thread waiting for subsequent writes is the expected behavior . Am i missing anything ? If so, it adds latency in the communication of messages between services. Is this acceptable ? This way it can impact the performance of the application. -- 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/3a088d23-74af-4fc7-9b02-c56e286b8fd7n%40googlegroups.com.
