Hi Pamb,
Do we have any update on this?
On Thursday, June 30, 2016 at 3:34:24 PM UTC+5, Lasantha wrote:
>
> Hello Carl,
>
> Thanks for the reply.
>
> Actually I was looking for some thing like
> https://github.com/Netflix/Hystrix. However Hystrix is specific to Java
> and it does not support
Sorry the concepts are a bit confusing. The Channel concept in Channelz
actually refers to "client". So, in a server application, you won't get
statistics about any gRPC client. GetServers method should give what you
need.
On Wednesday, June 3, 2020 at 5:36:27 AM UTC-7 ambigu...@gmail.com
Hi,
It seems like you are looking for help with usage of protobuf for repeated
fields.
protobuf has pretty good documentations for such stuff -
https://developers.google.com/protocol-buffers/docs/reference/cpp-generated#repeatedmessage
Hope that helps. Cheers!
On Sunday, May 31, 2020 at
Hi,
Thanks for the feedback, but this is not a gRPC setting. This probably
needs to be reported to GKE folks.
On Sunday, May 31, 2020 at 3:17:35 AM UTC-7 Thomas Barnekow wrote:
> I found the solution. The load balancer was configured with a default
> timeout of 30 seconds.
>
> Based on
Admittedly, set_buffer_hint() is not used much, and all it does is to
sometimes avoid immediate writes by the HTTP/2 transport in gRPC. Your
usecase does not seem one where this behavior is going to be useful.
To be clear, a write is considered to be "committed" when it passes flow
control in
Hi,
I'll try to be as clear and concise as possible.
1) Yes, channel, stub and completion queues can be shared across multiple
requests. Other classes such as ClientContext and reader/writer classes
would be specific for each request.
2) I would expect the stub to need to remain alive mainly
Hi there, did you got answer to your question? If yes could you tell what
tools are you using.
On Wednesday, March 9, 2016 at 4:54:22 AM UTC+5:30, mousum...@gmail.com
wrote:
>
> I am in the QA department. The application is written in Go and use gRPC
> proto along with GraphQL. I am looking
