Няма описание

Nicolas Noble d72df881d6 Merge pull request #8123 from ctiller/outstanding_sweeps преди 9 години
doc 500ca305b1 Merge pull request #4955 from ejona86/http-grpc-status-mapping преди 9 години
etc dbe8587c2a Merge pull request #7891 from jboeuf/new_ssl_certs преди 9 години
examples c9b401e3fc cpp examples missing gpr asserts преди 9 години
include 24869d558a Merge pull request #7996 from yang-g/canonical преди 9 години
src 3169a6d99b Merge pull request #8112 from dgquintas/lb_proto_sync преди 9 години
summerofcode d13a780be0 Add project overview for gsoc submission преди 9 години
templates 520ece60e5 switch distribtests to use nugets generated by dotnet cli преди 9 години
test 7bb547bd6e Merge pull request #8094 from ctiller/wait_to_start преди 9 години
third_party 47fab1fd62 Merge branch 'master' of github.com:grpc/grpc into lb_add_md преди 9 години
tools 8c985c2866 Allow more sync threads преди 9 години
vsprojects 24869d558a Merge pull request #7996 from yang-g/canonical преди 9 години
.clang-format a1cb002473 Make clang-format somewhat compatible across versions преди 11 години
.clang_complete 230e852935 Support clang_complete based editor plugins преди 9 години
.editorconfig ae66d78b8e Adding an editorconfig configuration file. преди 10 години
.gitignore 40beb37859 Fix CMake for Windows преди 9 години
.gitmodules b80d9c9626 Merge pull request #7594 from chedeti/grpc-thrift-v2 преди 9 години
.istanbul.yml 2af89e49cb Moved gRPC node package root to repo root, made it depend on grpc.gyp преди 10 години
.rspec d7e1a10628 Bundled C core with Ruby library преди 10 години
.travis.yml 10726f0421 Have Travis build the Sample app with frameworks too преди 9 години
.yardopts 33c728e1ed Adding a .yardopts file at the root so rubydocs isn't getting lost. преди 9 години
BUILD 24869d558a Merge pull request #7996 from yang-g/canonical преди 9 години
CMakeLists.txt 24869d558a Merge pull request #7996 from yang-g/canonical преди 9 години
CONTRIBUTING.md ecab5e2355 added more steps. преди 9 години
Gemfile d7e1a10628 Bundled C core with Ruby library преди 10 години
INSTALL.md 5fffa89805 php: remove reference to beta in INSTALL.md преди 9 години
LICENSE 6169d5f7b0 Update copyrights преди 9 години
MANIFEST.md ac586ba21e Remove tox преди 9 години
Makefile 24869d558a Merge pull request #7996 from yang-g/canonical преди 9 години
PATENTS 0f6aa52f4a Create PATENTS преди 10 години
PYTHON-MANIFEST.in 5998cd760c Add Python3.5 artifact targets преди 9 години
README.md a6091afe1c s/Beta/1.0 in languages status table преди 9 години
Rakefile 38ba85ce48 allow choosing config of ruby package builds from environment variable преди 9 години
binding.gyp 537f7c2a13 Revert "Grand unified closures" преди 9 години
build.yaml 24869d558a Merge pull request #7996 from yang-g/canonical преди 9 години
composer.json 35d8474c0e php: update composer.json преди 9 години
config.m4 537f7c2a13 Revert "Grand unified closures" преди 9 години
gRPC-Core.podspec a51f54192a Merge pull request #7559 from dgquintas/codegen_cleanse преди 9 години
gRPC-ProtoRPC.podspec 4a18c67b77 Move Podspecs to v1 преди 9 години
gRPC-RxLibrary.podspec 4a18c67b77 Move Podspecs to v1 преди 9 години
gRPC.podspec 4a18c67b77 Move Podspecs to v1 преди 9 години
grpc.bzl 24b2f67b80 Add copyright notice and documentation to .bzl file. преди 10 години
grpc.def e3817f4fd1 Merge branch 'master' of github.com:grpc/grpc into codegen_cleanse преди 9 години
grpc.gemspec a51f54192a Merge pull request #7559 from dgquintas/codegen_cleanse преди 9 години
package.json e1ee20bde6 Merge branch 'v1.0.x' of https://github.com/grpc/grpc into manual-upmerge преди 9 години
package.xml a51f54192a Merge pull request #7559 from dgquintas/codegen_cleanse преди 9 години
requirements.txt e5fd01a389 Bump python protobuf dependency to 3.0.0 преди 9 години
setup.cfg dd24c1ece4 Polish grpcio_health_checking package преди 9 години
setup.py 5928bff0c7 Merge branch 'v1.0.x' of https://github.com/grpc/grpc into manual-upmerge преди 9 години

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)

#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 are 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.