Ingen beskrivning

Mark D. Roth 9dab7d54a9 Fix deadlock. 9 år sedan
doc 0b259a8354 Merge remote-tracking branch 'upstream/master' into service_config 9 år sedan
etc 0e08b861a9 Updating roots from Mozilla. 9 år sedan
examples b9c77471f9 Merge pull request #8036 from tania-m/patch-1 9 år sedan
include 0b259a8354 Merge remote-tracking branch 'upstream/master' into service_config 9 år sedan
src 9dab7d54a9 Fix deadlock. 9 år sedan
summerofcode d13a780be0 Add project overview for gsoc submission 9 år sedan
templates 39b2e5bec6 PHP Proto3: update tests and README 9 år sedan
test d8f4a12482 Fix build problem in test. 9 år sedan
third_party 146a3773da PHP Proto3: upgrade protobuf to v3.1.0 and regenerate reflection.proto 9 år sedan
tools 30542c0b88 Merge remote-tracking branch 'upstream/master' into service_config 9 år sedan
vsprojects 30542c0b88 Merge remote-tracking branch 'upstream/master' into service_config 9 år sedan
.clang-format a1cb002473 Make clang-format somewhat compatible across versions 11 år sedan
.clang_complete 230e852935 Support clang_complete based editor plugins 9 år sedan
.editorconfig ae66d78b8e Adding an editorconfig configuration file. 11 år sedan
.gitignore 40beb37859 Fix CMake for Windows 9 år sedan
.gitmodules 87a1081211 Merge remote-tracking branch 'google/v1.0.x' into master-upmerge-from-deep-under 9 år sedan
.istanbul.yml 2af89e49cb Moved gRPC node package root to repo root, made it depend on grpc.gyp 10 år sedan
.rspec d7e1a10628 Bundled C core with Ruby library 10 år sedan
.travis.yml 10726f0421 Have Travis build the Sample app with frameworks too 9 år sedan
.yardopts 33c728e1ed Adding a .yardopts file at the root so rubydocs isn't getting lost. 10 år sedan
BUILD 0b259a8354 Merge remote-tracking branch 'upstream/master' into service_config 9 år sedan
CMakeLists.txt 0b259a8354 Merge remote-tracking branch 'upstream/master' into service_config 9 år sedan
CONTRIBUTING.md ecab5e2355 added more steps. 9 år sedan
Gemfile d7e1a10628 Bundled C core with Ruby library 10 år sedan
INSTALL.md 5fffa89805 php: remove reference to beta in INSTALL.md 9 år sedan
LICENSE 6169d5f7b0 Update copyrights 9 år sedan
MANIFEST.md ac586ba21e Remove tox 9 år sedan
Makefile 0b259a8354 Merge remote-tracking branch 'upstream/master' into service_config 9 år sedan
PATENTS 0f6aa52f4a Create PATENTS 10 år sedan
PYTHON-MANIFEST.in 5998cd760c Add Python3.5 artifact targets 9 år sedan
README.md a6091afe1c s/Beta/1.0 in languages status table 9 år sedan
Rakefile 38ba85ce48 allow choosing config of ruby package builds from environment variable 9 år sedan
binding.gyp 6600645135 Refactor hash table code into its own module and use it for method_config as well as method_config_table. 9 år sedan
build.yaml 30542c0b88 Merge remote-tracking branch 'upstream/master' into service_config 9 år sedan
composer.json 39b2e5bec6 PHP Proto3: update tests and README 9 år sedan
config.m4 6600645135 Refactor hash table code into its own module and use it for method_config as well as method_config_table. 9 år sedan
gRPC-Core.podspec 6600645135 Refactor hash table code into its own module and use it for method_config as well as method_config_table. 9 år sedan
gRPC-ProtoRPC.podspec 4a18c67b77 Move Podspecs to v1 9 år sedan
gRPC-RxLibrary.podspec 4a18c67b77 Move Podspecs to v1 9 år sedan
gRPC.podspec 4a18c67b77 Move Podspecs to v1 9 år sedan
grpc.bzl 24b2f67b80 Add copyright notice and documentation to .bzl file. 10 år sedan
grpc.def e3817f4fd1 Merge branch 'master' of github.com:grpc/grpc into codegen_cleanse 9 år sedan
grpc.gemspec 408913845c Merge remote-tracking branch 'upstream/master' into service_config 9 år sedan
package.json e1ee20bde6 Merge branch 'v1.0.x' of https://github.com/grpc/grpc into manual-upmerge 9 år sedan
package.xml 6600645135 Refactor hash table code into its own module and use it for method_config as well as method_config_table. 9 år sedan
requirements.txt e5fd01a389 Bump python protobuf dependency to 3.0.0 9 år sedan
setup.cfg dd24c1ece4 Polish grpcio_health_checking package 9 år sedan
setup.py 5928bff0c7 Merge branch 'v1.0.x' of https://github.com/grpc/grpc into manual-upmerge 9 år sedan

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.