Get desktop application:
View/edit binary Protocol Buffers messages
A service used to obtain stats for verifying LB behavior.
Gets the backend distribution for RPCs sent by a test client.
Request stats for the next num_rpcs sent by client.
If num_rpcs have not completed within timeout_sec, return partial results.
The number of completed RPCs for each peer.
The number of RPCs that failed to record a remote peer.
A service used to control reconnect server.
For reconnect interop test only. Client tells server what reconnection parameters it used.
For reconnect interop test only. Server tells client whether its reconnects are following the spec and the reconnect backoffs it saw.
A simple service to test the various types of RPCs and experiment with performance with various types of payload.
One empty request followed by one empty response.
One request followed by one response.
One request followed by one response. Response has cache control headers set such that a caching HTTP proxy (such as GFE) can satisfy subsequent requests.
One request followed by a sequence of responses (streamed download). The server returns the payload with client desired type and sizes.
A sequence of requests followed by one response (streamed upload). The server returns the aggregated size of client payload as the result.
Client-streaming request.
Optional input payload sent along with the request.
Whether the server should expect this request to be compressed. This field is "nullable" in order to interoperate seamlessly with servers not able to implement the full compression tests by introspecting the call to verify the request's compression status.
Client-streaming response.
Aggregated size of payloads received from the client.
A sequence of requests with each request served by the server immediately. As one request could lead to multiple responses, this interface demonstrates the idea of full duplexing.
A sequence of requests followed by a sequence of responses. The server buffers all the client requests and then serves them in order. A stream of responses are returned to the client when the server starts with first request.
The test server will not implement this method. It will be used to test the behavior when clients call unimplemented methods.
A simple service NOT implemented at servers so clients can test for that case.
A call that no server should implement
TODO(dgq): Go back to using well-known types once https://github.com/grpc/grpc/issues/6980 has been fixed. import "google/protobuf/wrappers.proto";
Used in:
, ,The bool value.
A protobuf representation for grpc status. This is used by test clients to specify a status that the server should attempt to return.
Used in:
,An empty message that you can re-use to avoid defining duplicated empty messages in your project. A typical example is to use it as argument or the return value of a service API. For instance: service Foo { rpc Bar (grpc.testing.Empty) returns (grpc.testing.Empty) { }; };
Used as request type in: ReconnectService.Stop, TestService.EmptyCall, TestService.UnimplementedCall, UnimplementedService.UnimplementedCall
Used as response type in: ReconnectService.Start, TestService.EmptyCall, TestService.UnimplementedCall, UnimplementedService.UnimplementedCall
(message has no fields)
The type of route that a client took to reach a server w.r.t. gRPCLB. The server must fill in "fallback" if it detects that the RPC reached the server via the "gRPCLB fallback" path, and "backend" if it detects that the RPC reached the server via "gRPCLB backend" path (i.e. if it got the address of this server from the gRPCLB server BalanceLoad RPC). Exactly how this detection is done is context and server dependent.
Used in:
Server didn't detect the route that a client took to reach it.
Indicates that a client reached a server via gRPCLB fallback.
Indicates that a client reached a server as a gRPCLB-given backend.
A block of data, to simply increase gRPC message size.
Used in:
, , , ,The type of data in body.
Primary contents of payload.
The type of payload that should be returned.
Used in:
, ,Compressable text format.
Configuration for a particular response.
Used in:
Desired payload sizes in responses from the server.
Desired interval between consecutive responses in the response stream in microseconds.
Whether to request the server to compress the response. This field is "nullable" in order to interoperate seamlessly with clients not able to implement the full compression tests by introspecting the call to verify the response's compression status.
Unary request.
Used as request type in: TestService.CacheableUnaryCall, TestService.UnaryCall
Desired payload type in the response from the server. If response_type is RANDOM, server randomly chooses one from other formats.
Desired payload size in the response from the server.
Optional input payload sent along with the request.
Whether SimpleResponse should include username.
Whether SimpleResponse should include OAuth scope.
Whether to request the server to compress the response. This field is "nullable" in order to interoperate seamlessly with clients not able to implement the full compression tests by introspecting the call to verify the response's compression status.
Whether server should return a given status
Whether the server should expect this request to be compressed.
Whether SimpleResponse should include server_id.
Whether SimpleResponse should include grpclb_route_type.
Unary response, as configured by the request.
Used as response type in: TestService.CacheableUnaryCall, TestService.UnaryCall
Payload to increase message size.
The user the request came from, for verifying authentication was successful when the client expected it.
OAuth scope.
Server ID. This must be unique among different server instances, but the same across all RPC's made to a particular server instance.
gRPCLB Path.
Server hostname.
Server-streaming request.
Used as request type in: TestService.FullDuplexCall, TestService.HalfDuplexCall, TestService.StreamingOutputCall
Desired payload type in the response from the server. If response_type is RANDOM, the payload from each response in the stream might be of different types. This is to simulate a mixed type of payload stream.
Configuration for each expected response message.
Optional input payload sent along with the request.
Whether server should return a given status
Server-streaming response, as configured by the request and parameters.
Used as response type in: TestService.FullDuplexCall, TestService.HalfDuplexCall, TestService.StreamingOutputCall
Payload to increase response size.