[grpc-io] Re: ClientBidiReactor or ClientCallbackReaderWriter

2020-12-16 Thread Christopher Pisz
For some reason, despite my including `/grpc/support/client_callback.h` my compiler doesn't know what ::grpc::ClientCallbackBidiReactor or any other class starting with ClientCallback, is. is there some define you need to get these to show up? On Friday, November 13, 2020 at 1:02:13 PM UTC-5

[grpc-io] rust

2020-12-16 Thread M D
plz add rust support too :/ -- 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

[grpc-io] Re: Can sync grpc tell me how many requests are not handled?

2020-12-16 Thread 'yas...@google.com' via grpc.io
That is a really good question! If you set memory limits via the resource quota, there are cases where incoming requests and connections are rejected due to unavailable memory quota. Unfortunately, this is not exposed as any metric right now (if I recall correctly). On Tuesday, December 8,

Re: [grpc-io] flow control problem in GRPC C++ release v1.25.0

2020-12-16 Thread 'yas...@google.com' via grpc.io
That's some really good investigation! Kudos! The transport layer (chttp2) does not really care whether the application is using the async API or the sync API. What matters really is whether there is a thread that is polling the underlying fds. For the sync API, this generally happens through