Hi, We have a use-case where there is one async streaming server sending messages to multiple clients in round-robin fashion. The data is not always available and need to wait for the producer to generate data before it can be sent out.
We followed the suggestions provided in the below article to overcome the behavior of task being added to the front of the completion queue and using alarms to wait for the producer - https://www.gresearch.co.uk/article/lessons-learnt-from-writing-asynchronous-streaming-grpc-services-in-c/ However, the approach is not elegant and adds the overhead of alarm tasks. Is this the suggested approach for async streaming or is there an alternative that we are missing? Thanks in advance for your response. -- 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/b40e1303-cfbd-4ccb-8524-d7c1e4edf2e4n%40googlegroups.com.
