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.
 
 
 
 
 
 
Dan Born a983dc7fc2 Merge fixups 8 years ago
doc manually fixed merge conflict. caused by the addition of a different new interop test 8 years ago
etc Updating roots from Mozilla. 8 years ago
examples php: require grpc extension to be installed before composer package 8 years ago
include Merge remote-tracking branch 'upstream/master' into fail_fast 8 years ago
src Merge fixups 8 years ago
summerofcode Add project overview for gsoc submission 8 years ago
templates Merge pull request #8182 from matt-kwong/fix_docker_local_clone 8 years ago
test Merge pull request #7664 from kpayson64/cv_wakeup_fd 8 years ago
third_party PHP Proto3: upgrade protobuf to v3.1.0 and regenerate reflection.proto 8 years ago
tools Merge pull request #8375 from jtattermusch/coreclr_benchmarks 8 years ago
vsprojects Moved cv polling into ev_poll_posix.c 8 years ago
.clang-format Make clang-format somewhat compatible across versions 10 years ago
.clang_complete Support clang_complete based editor plugins 9 years ago
.editorconfig Adding an editorconfig configuration file. 10 years ago
.gitignore Fix CMake for Windows 8 years ago
.gitmodules Merge remote-tracking branch 'google/v1.0.x' into master-upmerge-from-deep-under 8 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 Have Travis build the Sample app with frameworks too 9 years ago
.yardopts Adding a .yardopts file at the root so rubydocs isn't getting lost. 9 years ago
BUILD Moved cv polling into ev_poll_posix.c 8 years ago
CMakeLists.txt Moved cv polling into ev_poll_posix.c 8 years ago
CONTRIBUTING.md added more steps. 9 years ago
Gemfile Bundled C core with Ruby library 9 years ago
INSTALL.md php: remove reference to beta in INSTALL.md 8 years ago
LICENSE Update copyrights 9 years ago
MANIFEST.md Remove tox 9 years ago
Makefile Moved cv polling into ev_poll_posix.c 8 years ago
PATENTS Create PATENTS 10 years ago
PYTHON-MANIFEST.in Add Python3.5 artifact targets 8 years ago
README.md Update README.md 8 years ago
Rakefile allow choosing config of ruby package builds from environment variable 8 years ago
binding.gyp Moved cv polling into ev_poll_posix.c 8 years ago
build.yaml Moved cv polling into ev_poll_posix.c 8 years ago
composer.json php: require grpc extension to be installed before composer package 8 years ago
config.m4 Moved cv polling into ev_poll_posix.c 8 years ago
gRPC-Core.podspec Moved cv polling into ev_poll_posix.c 8 years ago
gRPC-ProtoRPC.podspec Move Podspecs to v1 8 years ago
gRPC-RxLibrary.podspec Move Podspecs to v1 8 years ago
gRPC.podspec Move Podspecs to v1 8 years ago
grpc.bzl Add copyright notice and documentation to .bzl file. 10 years ago
grpc.def Merge branch 'master' of github.com:grpc/grpc into codegen_cleanse 8 years ago
grpc.gemspec Moved cv polling into ev_poll_posix.c 8 years ago
package.json Bumping version to 1.0.1-pre1. 8 years ago
package.xml Moved cv polling into ev_poll_posix.c 8 years ago
requirements.txt Bump python protobuf dependency to 3.0.0 8 years ago
setup.cfg Polish grpcio_health_checking package 9 years ago
setup.py Merge branch 'v1.0.x' of https://github.com/grpc/grpc into manual-upmerge 8 years ago

README.md

Build Status

gRPC - An RPC library and framework

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

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