Get desktop application:
View/edit binary Protocol Buffers messages
One request followed by one response. The server returns the client payload as-is.
Repeated sequence of one request followed by one response. Should be called streaming ping-pong The server returns the client payload as-is on each response
Single-sided unbounded streaming from client to server The server returns the client payload as-is once the client does WritesDone
Single-sided unbounded streaming from server to client The server repeatedly returns the client payload as-is
Two-sided unbounded streaming between server to client Both sides send the content of their own choice to the other
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:
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.
Unary request.
Used as request type in: BenchmarkService.StreamingBothWays, BenchmarkService.StreamingCall, BenchmarkService.StreamingFromClient, BenchmarkService.StreamingFromServer, BenchmarkService.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.
Unary response, as configured by the request.
Used as response type in: BenchmarkService.StreamingBothWays, BenchmarkService.StreamingCall, BenchmarkService.StreamingFromClient, BenchmarkService.StreamingFromServer, BenchmarkService.UnaryCall
Payload to increase message size.
The user the request came from, for verifying authentication was successful when the client expected it.
OAuth scope.