Revert "Merge commit '4c51abf12053e3c43a62059c693322ea992b35ce' into main" This reverts commit 98137ddf9a4ca85fcf18ab1b4923fcf46e38748d. Reason for revert: this change was temporary, it is made to avoid breaking change" Original change's description: > Merge commit '4c51abf12053e3c43a62059c693322ea992b35ce' into main > > Removed Fuchsia specific local patch: templates/BUILD.gn.template and README.Fuchsia > > Copied BUILD.gn from https://fuchsia-review.git.corp.google.com/c/fuchsia/+/1151492 > > https://fuchsia.googlesource.com/third_party/grpc/+/4c51abf12053e3c43a62059c693322ea992b35ce is the head commit of tag/1.48.0-pre1 > Run git diff between this commit and 4c51abf12053e3c43a62059c693322ea992b35ce, the only diff is BUILD.gn. > > Note that this change is ONLY used for avoiding breaking change. It is a transition change for upreving gRPC to tag/1.48.0-pre1. > > Bug: 377536116 > > Change-Id: Ie4eefa0f9c2abecf051a856bd885fb6f905b0144 > Reviewed-on: https://fuchsia-review.googlesource.com/c/third_party/grpc/+/1151415 > Reviewed-by: Francois Rousseau <frousseau@google.com> Bug: 377536116 Change-Id: Icbd43ec7777b72e3040c3d002276fc8062f6e285 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://fuchsia-review.googlesource.com/c/third_party/grpc/+/1153895 Reviewed-by: RubberStamper 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Copyright 2015 Google Inc.
You can find more detailed documentation and examples in the doc and examples directories respectively.
See INSTALL for installation instructions for various platforms.
See tools/run_tests for more guidance on how to run various test suites (e.g. unit tests, interop tests, benchmarks)
See Performance dashboard for the performance numbers for the latest released version.
This repository contains source code for gRPC libraries for multiple languages written on top of shared C core library src/core.
Libraries in different languages may be in different states of development. We are seeking contributions for all of these libraries.
| Language | Source | Status |
|---|---|---|
| Shared C [core library] | src/core | 1.8 |
| C++ | src/cpp | 1.8 |
| Ruby | src/ruby | 1.8 |
| Python | src/python | 1.8 |
| PHP | src/php | 1.8 |
| C# | src/csharp | 1.8 |
| Objective-C | src/objective-c | 1.8 |
Java source code is in the grpc-java repository. Go source code is in the grpc-go repository. NodeJS source code is in the grpc-node repository.
See MANIFEST.md for a listing of top-level items in the repository.
Remote Procedure Calls (RPCs) provide a useful abstraction for building distributed applications and services. The libraries in this repository provide a concrete implementation of the gRPC protocol, layered over HTTP/2. These libraries enable communication between clients and servers using any combination of the supported languages.
Developers using gRPC typically start with the description of an RPC service (a collection of methods), and generate client and server side interfaces which they use on the client-side and implement on the server side.
By default, gRPC uses Protocol Buffers as the Interface Definition Language (IDL) for describing both the service interface and the structure of the payload messages. It is possible to use other alternatives if desired.
Starting from an interface definition in a .proto file, gRPC provides Protocol Compiler plugins that generate Client- and Server-side APIs. gRPC users typically call into these APIs on the Client side and implement the corresponding API on the server side.
Synchronous RPC calls, that block until a response arrives from the server, are the closest approximation to the abstraction of a procedure call that RPC aspires to.
On the other hand, networks are inherently asynchronous and in many scenarios, it is desirable to have the ability to start RPCs without blocking the current thread.
The gRPC programming surface in most languages comes in both synchronous and asynchronous flavors.
gRPC supports streaming semantics, where either the client or the server (or both) send a stream of messages on a single RPC call. The most general case is Bidirectional Streaming where a single gRPC call establishes a stream where both the client and the server can send a stream of messages to each other. The streamed messages are delivered in the order they were sent.
The gRPC protocol specifies the abstract requirements for communication between clients and servers. A concrete embedding over HTTP/2 completes the picture by fleshing out the details of each of the required operations.
A gRPC RPC comprises of a bidirectional stream of messages, initiated by the client. In the client-to-server direction, this stream begins with a mandatory Call Header, followed by optional Initial-Metadata, followed by zero or more Payload Messages. The server-to-client direction contains an optional Initial-Metadata, followed by zero or more Payload Messages terminated with a mandatory Status and optional Status-Metadata (a.k.a.,Trailing-Metadata).
The abstract protocol defined above is implemented over HTTP/2. gRPC bidirectional streams are mapped to HTTP/2 streams. The contents of Call Header and Initial Metadata are sent as HTTP/2 headers and subject to HPACK compression. Payload Messages are serialized into a byte stream of length prefixed gRPC frames which are then fragmented into HTTP/2 frames at the sender and reassembled at the receiver. Status and Trailing-Metadata are sent as HTTP/2 trailing headers (a.k.a., trailers).
gRPC inherits the flow control mechanisms in HTTP/2 and uses them to enable fine-grained control of the amount of memory used for buffering in-flight messages.
