Get desktop application:
View/edit binary Protocol Buffers messages
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. The server returns the client payload as-is.
Unary request.
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. If response_type is COMPRESSABLE, this denotes the size before compression.
Optional input payload sent along with the request.
Whether SimpleResponse should include username.
Whether SimpleResponse should include OAuth scope.
Whether server should return a given status
Unary response, as configured by the request.
Payload to increase message size.
The user the request came from, for verifying authentication was successful when the client expected it.
OAuth scope.
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.
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.
A simple service NOT implemented at servers so clients can test for that case.
A call that no server should implement
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:
,Used as request type in: TestService.EmptyCall, UnimplementedService.UnimplementedCall
Used as response type in: TestService.EmptyCall, UnimplementedService.UnimplementedCall
(message has no fields)
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.
Uncompressable binary format.
Randomly chosen from all other formats defined in this enum.
Configuration for a particular response.
Used in:
Desired payload sizes in responses from the server. If response_type is COMPRESSABLE, this denotes the size before compression.
Desired interval between consecutive responses in the response stream in microseconds.
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.