Bez popisu

Jan Tattermusch 2133a552d0 prepopulate more pip packages on kokoro linux před 8 roky
.github e395dfbcad Set owners for client_channel tree. před 8 roky
.vscode d1f3082ff6 Adding shim for debugging node tests using vscode. před 8 roky
bazel 4280725bb3 Clean up grpc++_unsecure so that it doesn't require secure content anymore před 8 roky
cmake d996379030 Reset OWNERS state před 8 roky
doc 309f20802d Update env var doc před 8 roky
etc 69c923ffb7 Updating roots from Mozilla. před 8 roky
examples d996379030 Reset OWNERS state před 8 roky
include b667f12cef Merge pull request #11979 from apolcyn/ensure_cancel_with_status_memory_api před 8 roky
src 9279ca1267 Merge pull request #11796 from afirago/fix-fallthrough-werror před 8 roky
summerofcode d13a780be0 Add project overview for gsoc submission před 9 roky
templates 2b7c4ddfcc Install Android SDK tools in Dockerfile před 8 roky
test ab04027e47 Merge branch 'master' of https://github.com/grpc/grpc into flow-control-v3 před 8 roky
third_party 882ba60fcb Merge remote-tracking branch 'upstream/v1.4.x' into master_1.4.1_upmerge před 8 roky
tools 2133a552d0 prepopulate more pip packages on kokoro linux před 8 roky
vsprojects fe8f5bc8e9 regenerate projects před 8 roky
.clang-format a1cb002473 Make clang-format somewhat compatible across versions před 10 roky
.clang_complete ed38016565 C++ compatibility fixes před 8 roky
.editorconfig ae66d78b8e Adding an editorconfig configuration file. před 10 roky
.gitignore 13c0e6e549 Update .gitignore před 8 roky
.gitmodules 97106a7ef2 Removed 3rd party dep on thrift před 8 roky
.istanbul.yml 2af89e49cb Moved gRPC node package root to repo root, made it depend on grpc.gyp před 10 roky
.pylintrc 69b7231776 gRPC Python test infrastructure před 8 roky
.rspec d7e1a10628 Bundled C core with Ruby library před 10 roky
.travis.yml 10726f0421 Have Travis build the Sample app with frameworks too před 9 roky
.yardopts 33c728e1ed Adding a .yardopts file at the root so rubydocs isn't getting lost. před 9 roky
AUTHORS 312ea4a187 change LICENSE, add AUTHORS před 8 roky
BUILD ab04027e47 Merge branch 'master' of https://github.com/grpc/grpc into flow-control-v3 před 8 roky
CMakeLists.txt fe8f5bc8e9 regenerate projects před 8 roky
CODE-OF-CONDUCT.md c055a79262 Fix code of conduct před 8 roky
CONTRIBUTING.md d89248f51c improve CONTRIBUTING.md and add rules for PRs před 8 roky
Gemfile d7e1a10628 Bundled C core with Ruby library před 10 roky
INSTALL.md a38562e8e9 Fix dependency download link in INSTALL.md to use https před 8 roky
LICENSE fbb61ed25d fix license file před 8 roky
MANIFEST.md ac586ba21e Remove tox před 9 roky
Makefile fe8f5bc8e9 regenerate projects před 8 roky
NOTICE.txt 312ea4a187 change LICENSE, add AUTHORS před 8 roky
OWNERS aa49cbfd9d Add policy to comment před 8 roky
PYTHON-MANIFEST.in 1f24b2ad8a Changes před 8 roky
README.md a858990b22 Update perf link. před 8 roky
Rakefile 7aa184bb42 specify mingw g++ compiler for ruby windows artifact build před 8 roky
WORKSPACE 736907c23e Reverted submodule changes... před 8 roky
binding.gyp fb193a1e2f Merge branch 'master' of https://github.com/grpc/grpc into flow-control-v3 před 8 roky
build.yaml ab04027e47 Merge branch 'master' of https://github.com/grpc/grpc into flow-control-v3 před 8 roky
build_config.rb 7897ae9308 auto-fix most of licenses před 8 roky
composer.json bb3d95b643 Use https://grpc.io consistently as the canonical URL před 8 roky
config.m4 268a82398c Pull flow control into one module před 8 roky
config.w32 268a82398c Pull flow control into one module před 8 roky
gRPC-Core.podspec ab04027e47 Merge branch 'master' of https://github.com/grpc/grpc into flow-control-v3 před 8 roky
gRPC-ProtoRPC.podspec bb3d95b643 Use https://grpc.io consistently as the canonical URL před 8 roky
gRPC-RxLibrary.podspec bb3d95b643 Use https://grpc.io consistently as the canonical URL před 8 roky
gRPC.podspec bb3d95b643 Use https://grpc.io consistently as the canonical URL před 8 roky
grpc.bzl 4d5c3102a1 fix remaining license notices před 8 roky
grpc.def c18b9069cd Merge remote-tracking branch 'upstream/v1.3.x' into master_1.3.x_upmerge před 8 roky
grpc.gemspec ab04027e47 Merge branch 'master' of https://github.com/grpc/grpc into flow-control-v3 před 8 roky
package.json 4c3360c3fb Adding platform and abi tags in our node-pre-gyp. před 8 roky
package.xml ab04027e47 Merge branch 'master' of https://github.com/grpc/grpc into flow-control-v3 před 8 roky
requirements.txt b38aac4c76 Bump protobuf to 3.2.0 před 8 roky
setup.cfg 06dea573da Enable running Python formatting před 8 roky
setup.py 9c420447fa Add classifiers to package details před 8 roky

README.md

Build Status

gRPC - An RPC library and framework

Copyright 2015 Google Inc.

Documentation

You can find more detailed documentation and examples in the doc and examples directories respectively.

Installation & Testing

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.

Repository Structure & Status

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.0
C++ src/cpp 1.0
Ruby src/ruby 1.0
NodeJS src/node 1.0
Python src/python 1.0
PHP src/php 1.0
C# src/csharp 1.0
Objective-C src/objective-c 1.0

Java source code is in the grpc-java repository. Go source code is in the grpc-go repository.

See MANIFEST.md for a listing of top-level items in the repository.

Overview

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.

Interface

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.

Surface API

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 vs. asynchronous

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.

Streaming

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.

Protocol

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.

Abstract gRPC protocol

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).

Implementation over HTTP/2

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).

Flow Control

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.