You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 16, 2020. It is now read-only.
As described in linkerd/linkerd2#2269, there are situations where a client or server may wish to issue PING messages and be notified when the remote peer has responded. This can be useful to discover network latencies and to instrument failure detection.
I imagine this being exposed as, effectively, a Service<Bytes, Response = Bytes> for each connection.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As described in linkerd/linkerd2#2269, there are situations where a client or server may wish to issue PING messages and be notified when the remote peer has responded. This can be useful to discover network latencies and to instrument failure detection.
I imagine this being exposed as, effectively, a
Service<Bytes, Response = Bytes>
for each connection.The text was updated successfully, but these errors were encountered: