Re: [grpc-io] Re: gRFC Proposal L12: Node.js gRPC 2.0 API changes

2017-12-12 Thread 'Michael Lumish' via grpc.io
Thank you for your input. Regarding the Protobuf.js changes, one of the primary goals of this API change is to decouple gRPC from Protobuf.js as much as possible, because the existing tight coupling has prevented us from upgrading the dependency from Protobuf.js 5 to 6 without breaking the API.

[grpc-io] Re: Error handling in GRPC (C++ primarily)

2017-12-12 Thread Evan Jones
I think the "right" option is going to depends on your situation and point of view: *1. This is totally acceptable* To be able to handle errors from Login, I need to understand the application. Therefore, I can't reuse any of the error handling code between this request and other requests,

[grpc-io] Re: Java gRPC - conditional forwarding server interceptor

2017-12-12 Thread 'Kun Zhang' via grpc.io
I am not sure I understand what you are trying to do. Are you trying to create a proxy? A proxy wouldn't need server interceptor. Instead, you can use a dynamic fallback handler registery . It

[grpc-io] Re: Custom Transport Security

2017-12-12 Thread 'Carl Mastrangelo' via grpc.io
Responses inline: On Wednesday, December 6, 2017 at 7:28:05 AM UTC-8, aaj...@gmail.com wrote: > > Ya I was looking through the C core a bit last night and following through > how SSL works. It definitely looks possible. > > That seems reasonable, are there any future plans to make such an API >

[grpc-io] Load balancing in multi server setup with single client connections for multiple RPC calls

2017-12-12 Thread Manjunath Shetty H
Hi All, As per i understand it is good practice to use single gRPC connection for multiple concurrent RPC calls. So in my setup (kubernetes) , i have multiple instances of the server. When i create a connection using grpc client, it will go through the default k8s load balancer and it will be

[grpc-io] Error handling in GRPC (C++ primarily)

2017-12-12 Thread pavol . ostertag
Hello, Two of our teams independently defined several RPC calls. Both wanted to cover this usecase: We have situation when command did not do what the caller wanted. For example (it is just an example, we do not have such code): service Users { rpc Login(loginRequest) returns