Re: [grpc-io] Re: (golang) Detecting a dead client

On Wed, Aug 30, 2017 at 1:39 AM, wrote: > Was the heartbeat solution ever implemented? > See https://godoc.org/google.golang.org/grpc#KeepaliveParams . ServerParameters.Time and Timeout. -- You received this message because you are subscribed to the Google Groups

Re: [grpc-io] Re: (golang) Detecting a dead client

This solution doesn't seem to work. Just tested with a server and client running locally. Killing the client process did not trigger a context.Done() call. Here's the very basic code from the server: func (s *server) Listen(_ *service.ListenRequest, ls service.MyService_ListenServer) error {

Re: [grpc-io] Re: (golang) Detecting a dead client

Just a notice for future readers. As today (2017.07.25) it's enough to listen on context.Done(). func (p *XImpl) Listen(_ *empty.Empty, rec services.X_ListenServer) error { c := make(chan *services.X, 16) p.add(c) defer p.remove(c) ctx := rec.Context() for { select { case v := <-c: if err :=

Re: [grpc-io] Re: (golang) Detecting a dead client

We will have heart-beat mechanism ready to tackle this kind of issues soon (Q1 2017). On Tue, Dec 13, 2016 at 10:32 AM, Paul Breslin wrote: > This seems to still be an issue. We have a server side stream read > implementation that is forced to manually timeout because

[grpc-io] Re: (golang) Detecting a dead client

This seems to still be an issue. We have a server side stream read implementation that is forced to manually timeout because the Done channel doesn't notify when the client side goes away. On Tuesday, October 27, 2015 at 6:50:35 PM UTC-4, Aaron Beitch wrote: > > Hello, > > tl;dr: Does HTTP2