Great, here’s some feature requests (now that I am sure I have the right forum):
1) Add an async streaming example to your cpp example code. Launching a thread per connection is somewhat wasteful, so streaming and async go hand in hand. It is a large omission. 2) When c++ grpc app is spinning on cq->next, it serves clients in a non-uniform manner. A *very* non-uniform manner. Clients can starve. This should be addressed, as it does not seem like an uncommon use case. 3) AsyncNext takes a deadline. If that deadline is 0 (using any gpr_clock_type) I expect it to return immediately if there is nothing in the queue. This happens for GPR_CLOCK_PRECISE but for no others. There should simply be a TryNext method. 4) It would be nice if there was some way to specify socket options. ie TCP_NODELAY and other such options should be readily accessible. Not supporting this is more than just an inconvenience for a programmer imo. Also, please clarify the threads grpc launches at startup (for C++, or in general if it is all the same). Can you enumerate them and briefly discuss their purpose? Thank you so 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/24420f2c-b80a-44b7-8d07-01403ce29ee2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
