googleapis/google/rpc
Google APIs 02362883cd fix: add http_proto dependency to rpc_java_proto
PiperOrigin-RevId: 910227360
2026-05-04 13:59:07 -07:00
..
context feat: add origin to AttributeContext.Request 2026-03-31 15:15:00 -07:00
BUILD.bazel fix: add http_proto dependency to rpc_java_proto 2026-05-04 13:59:07 -07:00
code.proto feat: add origin to AttributeContext.Request 2026-03-31 15:15:00 -07:00
error_details.proto feat: add origin to AttributeContext.Request 2026-03-31 15:15:00 -07:00
http.proto feat: add origin to AttributeContext.Request 2026-03-31 15:15:00 -07: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 origin to AttributeContext.Request 2026-03-31 15:15:00 -07: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.