The C based gRPC (C++, Python, Ruby, Objective-C, PHP, C#) https://grpc.io/
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Stanley Cheung 77fae2784e fix broken links 9 years ago
doc fix broken links 9 years ago
etc Revert "Refreshing the etc/roots.pem file." 9 years ago
examples Update base INSTALL to markdown and remove outdated content 9 years ago
include Always ref writable streams 9 years ago
src Merge pull request #5541 from jtattermusch/python_split_tests 9 years ago
summerofcode More ideas page tweaks 9 years ago
templates Added comment for gyp 9 years ago
test Always ref writable streams 9 years ago
third_party update nanopb version 9 years ago
tools increase timeout for interop tests 9 years ago
vsprojects Merge pull request #5293 from dgquintas/alarm_cpp 9 years ago
.clang-format Make clang-format somewhat compatible across versions 10 years ago
.editorconfig Adding an editorconfig configuration file. 10 years ago
.gitignore Faster code generation 9 years ago
.gitmodules Revert "Revert "Proto API for LB request/responses"" 9 years ago
.istanbul.yml Moved gRPC node package root to repo root, made it depend on grpc.gyp 9 years ago
.rspec Bundled C core with Ruby library 9 years ago
.travis.yml Updated travis to use Xcode 7.2 and SDK 9.2 9 years ago
.yardopts Adding a .yardopts file at the root so rubydocs isn't getting lost. 9 years ago
BUILD Merge pull request #5293 from dgquintas/alarm_cpp 9 years ago
CONTRIBUTING.md Update base INSTALL to markdown and remove outdated content 9 years ago
Gemfile Bundled C core with Ruby library 9 years ago
INSTALL.md bit of text change 9 years ago
LICENSE Happy new year 9 years ago
MANIFEST.md Rename INVENTORY.md to MANIFEST.md 9 years ago
Makefile Merge pull request #5293 from dgquintas/alarm_cpp 9 years ago
PATENTS Create PATENTS 10 years ago
PYTHON-MANIFEST.in Exclude cygrpc.so from the Python package 9 years ago
README.md Update base INSTALL to markdown and remove outdated content 9 years ago
Rakefile 2.1.6 doesn't work on MacOS (wheee...) 9 years ago
binding.gyp Merge github.com:grpc/grpc into naming-crisis 9 years ago
build.yaml Merge pull request #5293 from dgquintas/alarm_cpp 9 years ago
composer.json php: bump version 9 years ago
config.m4 add some CFLAGS to compile on mac 9 years ago
gRPC.podspec Merge github.com:grpc/grpc into naming-crisis 9 years ago
grpc.bzl Add copyright notice and documentation to .bzl file. 10 years ago
grpc.def Always ref writable streams 9 years ago
grpc.gemspec Merge github.com:grpc/grpc into naming-crisis 9 years ago
package.json Faster code generation 9 years ago
package.xml sync php with core version; 9 years ago
requirements.txt Use wheels instead for custom bdists 9 years ago
setup.cfg Mitigate Python build directory naming conflict 9 years ago
setup.py Merge branch 'master' into backport-merge 9 years ago
tox.ini Use tox commands to run interop client/server 9 years ago

README.md

Build Status

gRPC - An RPC library and framework

Join the chat at https://gitter.im/grpc/grpc

Copyright 2015-2016 Google Inc.

#Documentation

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

#Installation

See INSTALL for installation instructions for various platforms.

#Repository Structure & Status

This repository contains source code for gRPC libraries for multiple languages written on top of shared C core library [src/core] (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] (src/core) Beta - the surface API is stable
C++ [src/cpp] (src/cpp) Beta - the surface API is stable
Ruby [src/ruby] (src/ruby) Beta - the surface API is stable
NodeJS [src/node] (src/node) Beta - the surface API is stable
Python [src/python] (src/python) Beta - the surface API is stable
PHP [src/php] (src/php) Beta - the surface API is stable
C# [src/csharp] (src/csharp) Beta - the surface API is stable
Objective-C [src/objective-c] (src/objective-c) Beta - the surface API is stable
Java source code is in the [grpc-java] (http://github.com/grpc/grpc-java) repository. Go source code is in the [grpc-go] (http://github.com/grpc/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.