Home
last modified time | relevance | path

Searched refs:backoffs (Results 1 – 6 of 6) sorted by relevance

/third_party/grpc/doc/
Dconnection-backoff-interop-test-description.md5 backoffs as specified in
17 6. The client checks the response to see whether the server thinks the backoffs
18 are conforming the spec or do its own check on the backoffs in the response.
32 * The server port to connect to for testing backoffs. For example, "8081"
36 returned backoff status or check the returned backoffs on its own.
43 reconnections with proper backoffs. A convenient way to achieve this is to
46 4. Checks the response to see whether the server thinks the backoffs passed the
48 5. Optionally, the client can do its own check on the returned backoffs.
62 all the reconnection timestamps and return the connection backoffs in the
63 response in milliseconds. The server also checks the backoffs to see whether
Dconnection-backoff.md11 1. JITTER (by how much to randomize backoffs).
45 Alternate implementations must ensure that connection backoffs started at the
/third_party/libwebsockets/lib/secure-streams/
Dprivate-lib-secure-streams.h359 typedef struct backoffs { struct
360 struct backoffs *next; argument
/third_party/grpc/src/objective-c/tests/RemoteTestClient/
Dmessages.proto166 // reconnect backoffs it saw.
/third_party/grpc/src/proto/grpc/testing/
Dmessages.proto191 // reconnect backoffs it saw.
/third_party/lwip/
DCHANGELOG4533 - TCP retransmission timeout backoffs are not correctly computed