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(), and we have to maintain a queue where all application threads adds messages into it and proceed with execution of next instructions and grpc[client/server] thread reads from it each time a tag is received from Completion queue and sends to peer service. This way, it adds latency in the communication of messages between services. Is this acceptable ? Is there any better way of doing it ? -- 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/ad87f7f2-bd5d-4c24-b304-a1e784dc68a3n%40googlegroups.com.
