Re: [grpc-io] [grpc-go] why use independent goroutine keepalive rather then conn.setReadDeadline?

[Eric Anderson]

When the keepalive timer expires (and there's been no activity; most expirations will have activity and so it will just re-set the timer), the connection isn't killed. Instead, a write is done on the connection. If a read happens within the timeout, then everything is deemed good and it waits until the next expiration without read activity. So it's quite different from setReadDeadline.

On Wed, Jun 7, 2017 at 11:56 PM, Zeymo Wang <zeymo...@gmail.com> wrote:

Is any consider？

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to grp...@googlegroups.com.
Visit this group at https://groups.google.com/group/grpc-io.
To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/12c86390-6125-4103-9614-7b758446372f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.