[grpc-io] Re: New look for gRPC!

Thanks for sharing. I like how the new logo helps to better identify "RPC" by having a lowercase "g", seems more meaningful. On Thursday, April 12, 2018 at 8:11:10 PM UTC+2, April Kyle Nassi wrote: > > Hi all, > > You may have heard earlier that we've been working with CNCF on a new look > for g

[grpc-io] Resetting deadline on streaming RPC

I have a streaming RPC that reports back a progress message to a client. Right now a deadline of 10 seconds is set, however, the time it takes for the RPC to complete might very well exceed 10 seconds. Questions: 1. Is there a way to reset the client context deadline timer when I receive a str

[grpc-io] Re: Clarification on gRPC AsyncNext usage

Sorry for the delayed response. You should take a look at greeter_async_client2.cc , it is a good example of client code that has a dedicated thread to drive work forward on RPCs. In the main body of the

[grpc-io] gRPC Core 1.11.0 "gorgeous" has been released

I'm thrilled to announce that gRPC Core 1.11.0 (*gorgeous *) has been released! This extends to C++, C#, Python, Ruby, Objective-C, PHP and Node.js. Refer to the release notes

[grpc-io] Internal OpenSSL initialization affecting the application

Hi, I recently pinned down a sporadic race condition in my application due to grpc intializing OpenSSL internally. The problem is that OpenSSL has some global callbacks that grpc is trying to initialize on it's own without the authorization of the application. The problem is in the init_openss

Re: [grpc-io] Resetting deadline on streaming RPC

On Mon, Apr 16, 2018 at 5:31 AM, Robert Bielik wrote: > I have a streaming RPC that reports back a progress message to a client. > Right now a deadline of 10 seconds is set, however, the time it takes for > the RPC to complete might very well exceed 10 seconds. > > Questions: > 1. Is there a way

Re: [grpc-io] Re: [grpc-java] global exception handler on client-side

On Sat, Apr 14, 2018 at 5:49 AM, evaliauka via grpc.io < grpc-io@googlegroups.com> wrote: > What I want is to setup an exception converter once, and have it applied > automatically to all grpc calls. > grpc-java doesn't support this, and it would be a bit weird because it changes the API. Maybe i

[grpc-io] Re: [Java] Server-side streaming - server doesn't detect when client disappears

I suppose my previous post was overly verbose, so I'll pose a more succinct question instead: In a gRPC server stream, what is the expected behavior on the server side when the client disconnects (either gracefully or due to some unknown reason) ? Assuming keepalive is set on both client & serv

Re: [grpc-io] Re: [Java] Server-side streaming - server doesn't detect when client disappears

On Fri, Apr 13, 2018 at 3:32 PM, Christopher Schechter wrote: > Inside testService, it has this server-side streaming method: > > // for the purpose of this test, this queue is pre-filled with a handful > of StreamItems, and never has any other objects added to it > BlockingQueue queue = new Link

Re: [grpc-io] Re: [Java] Server-side streaming - server doesn't detect when client disappears

Oh, and if you want a notification for your code, you could use Context.current().addListener(). That should be firing, as it isn't synchronized with the rest of the callbacks. On Mon, Apr 16, 2018 at 5:27 PM, Eric Anderson wrote: > On Fri, Apr 13, 2018 at 3:32 PM, Christopher Schechter < > chri