googleapis/google/rpc
Google APIs 736857e7a6 chore: update README files
PiperOrigin-RevId: 572611639
2023-10-11 10:16:35 -07:00
..
context chore(php): remove non-ads php_grpc_library targets 2023-05-30 17:06:44 -07:00
BUILD.bazel chore: configure common protos for PHP 2023-04-10 12:19:07 -07:00
code.proto feat: Add the google.rpc.context.AuditContext and google.rpc.http message to the open source 2022-12-13 23:06:35 -08:00
error_details.proto feat: Add the google.rpc.context.AuditContext and google.rpc.http message to the open source 2022-12-13 23:06:35 -08:00
http.proto feat: Add the google.rpc.context.AuditContext and google.rpc.http message to the open source 2022-12-13 23:06:35 -08:00
README.md chore: update README files 2023-10-11 10:16:35 -07:00
rpc_publish.yaml Synchronize new proto/yaml changes. 2019-11-01 13:39:38 -07:00
status.proto feat: Add the google.rpc.context.AuditContext and google.rpc.http message to the open source 2022-12-13 23:06:35 -08:00

RPC (Remote Procedure Call) Types

This package contains protocol buffer types that represent remote procedure call concepts. While gRPC uses these types, we encourage their use in any interested RPC implementation to promote compatibility and consistency.

Key Concepts

  • Code: An enum that represents an error code returned by an RPC. These error codes map to HTTP codes, but are slightly finer-grained. Every gRPC code has exactly one corresponding HTTP code; however, some HTTP codes have more than one corresponding gRPC code.
  • Error details: Any of the types contained in error_details.proto which provide extra details about particular types of failures.
  • Status: Combines a code, message, and error details to represent the success or failure details of an RPC call.