2015-05-07 07:15:53 +08:00
gRPC-Java - An RPC library and framework
========================================
2015-08-12 02:39:07 +08:00
[![Build Status ](https://travis-ci.org/grpc/grpc-java.svg?branch=master )](https://travis-ci.org/grpc/grpc-java)
[![Coverage Status ](https://coveralls.io/repos/grpc/grpc-java/badge.svg?branch=master&service=github )](https://coveralls.io/github/grpc/grpc-java?branch=master)
2015-05-16 02:57:05 +08:00
gRPC-Java works with JDK 6. TLS usage typically requires using Java 8, or Play
2015-05-29 04:12:56 +08:00
Services Dynamic Security Provider on Android. Please see the [Security
Readme](SECURITY.md).
2014-12-16 02:24:42 +08:00
2015-05-27 05:22:32 +08:00
Download
--------
Download [the JAR][]. Or for Maven, add to your `pom.xml` :
```xml
< dependency >
< groupId > io.grpc< / groupId >
< artifactId > grpc-all< / artifactId >
2015-08-14 06:49:22 +08:00
< version > 0.8.0< / version >
2015-05-27 05:22:32 +08:00
< / dependency >
```
Or for Gradle, add to your dependencies:
```gradle
2015-08-14 06:49:22 +08:00
compile 'io.grpc:grpc-all:0.8.0'
2015-05-27 05:22:32 +08:00
```
2015-08-14 06:49:22 +08:00
[the JAR]: https://search.maven.org/remote_content?g=io.grpc& a=grpc-all& v=0.8.0
2015-05-27 05:22:32 +08:00
Development snapshots are available in [Sonatypes's snapshot
repository](https://oss.sonatype.org/content/repositories/snapshots/).
For protobuf-based codegen integrated with the Maven build system, you can use
[maven-protoc-plugin][]:
```xml
2015-07-01 09:13:27 +08:00
< pluginRepositories >
< pluginRepository >
< releases >
< updatePolicy > never< / updatePolicy >
< / releases >
< snapshots >
< enabled > false< / enabled >
< / snapshots >
< id > central< / id >
< name > Central Repository< / name >
< url > https://repo.maven.apache.org/maven2< / url >
< / pluginRepository >
< pluginRepository >
< id > protoc-plugin< / id >
< url > https://dl.bintray.com/sergei-ivanov/maven/< / url >
< / pluginRepository >
< / pluginRepositories >
2015-05-27 05:22:32 +08:00
< build >
< extensions >
< extension >
< groupId > kr.motd.maven< / groupId >
< artifactId > os-maven-plugin< / artifactId >
2015-09-17 03:52:26 +08:00
< version > 1.4.0.Final< / version >
2015-05-27 05:22:32 +08:00
< / extension >
< / extensions >
< plugins >
< plugin >
< groupId > com.google.protobuf.tools< / groupId >
< artifactId > maven-protoc-plugin< / artifactId >
< version > 0.4.2< / version >
< configuration >
2015-07-23 00:19:52 +08:00
<!--
The version of protoc must match protobuf-java. If you don't depend on
protobuf-java directly, you will be transitively depending on the
protobuf-java version that grpc depends on.
-->
2015-08-14 06:49:22 +08:00
< protocArtifact > com.google.protobuf:protoc:3.0.0-alpha-3.1:exe:${os.detected.classifier}< / protocArtifact >
2015-05-27 05:22:32 +08:00
< pluginId > grpc-java< / pluginId >
2015-08-14 06:49:22 +08:00
< pluginArtifact > io.grpc:protoc-gen-grpc-java:0.8.0:exe:${os.detected.classifier}< / pluginArtifact >
2015-05-27 05:22:32 +08:00
< / configuration >
< executions >
< execution >
< goals >
< goal > compile< / goal >
< goal > compile-custom< / goal >
< / goals >
< / execution >
< / executions >
< / plugin >
< / plugins >
< / build >
```
[maven-protoc-plugin]: http://sergei-ivanov.github.io/maven-protoc-plugin/
For protobuf-based codegen integrated with the Gradle build system, you can use
[protobuf-gradle-plugin][]:
```gradle
2015-07-23 00:19:52 +08:00
apply plugin: 'java'
2015-05-27 05:22:32 +08:00
apply plugin: 'com.google.protobuf'
buildscript {
repositories {
mavenCentral()
}
dependencies {
2015-08-04 02:10:22 +08:00
classpath 'com.google.protobuf:protobuf-gradle-plugin:0.6.1'
2015-05-27 05:22:32 +08:00
}
}
2015-07-23 00:19:52 +08:00
protobuf {
protoc {
// The version of protoc must match protobuf-java. If you don't depend on
// protobuf-java directly, you will be transitively depending on the
// protobuf-java version that grpc depends on.
2015-08-14 06:49:22 +08:00
artifact = "com.google.protobuf:protoc:3.0.0-alpha-3.1"
2015-07-23 00:19:52 +08:00
}
plugins {
grpc {
2015-08-14 06:49:22 +08:00
artifact = 'io.grpc:protoc-gen-grpc-java:0.8.0'
2015-07-23 00:19:52 +08:00
}
}
generateProtoTasks {
all()*.plugins {
grpc {}
2015-05-27 05:22:32 +08:00
}
}
}
```
[protobuf-gradle-plugin]: https://github.com/google/protobuf-gradle-plugin
2015-01-30 07:00:58 +08:00
How to Build
------------
2015-08-14 23:49:56 +08:00
If you are making changes to gRPC-Java, see the [compiling
instructions](COMPILING.md).
2015-05-13 08:03:19 +08:00
2015-01-30 07:00:58 +08:00
Navigating Around the Source
----------------------------
2015-08-08 14:28:06 +08:00
Here's a quick readers' guide to the code to help folks get started. At a high
2015-08-06 07:48:15 +08:00
level there are three distinct layers to the library: __Stub__ , __Channel__ &
__Transport__.
2014-12-16 02:24:42 +08:00
2015-01-30 07:00:58 +08:00
### Stub
2014-12-16 02:24:42 +08:00
2015-08-06 07:48:15 +08:00
The Stub layer is what is exposed to most developers and provides type-safe
bindings to whatever datamodel/IDL/interface you are adapting. gRPC comes with
a [plugin ](https://github.com/google/grpc-java/blob/master/compiler ) to the
protocol-buffers compiler that generates Stub interfaces out of `.proto` files,
but bindings to other datamodel/IDL should be trivial to add and are welcome.
2014-12-16 02:24:42 +08:00
#### Key Interfaces
2015-01-28 02:25:39 +08:00
[Stream Observer ](https://github.com/google/grpc-java/blob/master/stub/src/main/java/io/grpc/stub/StreamObserver.java )
2014-12-16 02:24:42 +08:00
2015-01-30 07:00:58 +08:00
### Channel
2014-12-16 02:24:42 +08:00
2015-08-06 07:48:15 +08:00
The Channel layer is an abstraction over Transport handling that is suitable for
interception/decoration and exposes more behavior to the application than the
Stub layer. It is intended to be easy for application frameworks to use this
layer to address cross-cutting concerns such as logging, monitoring, auth etc.
Flow-control is also exposed at this layer to allow more sophisticated
applications to interact with it directly.
2014-12-16 02:24:42 +08:00
#### Common
2015-01-28 02:25:39 +08:00
* [Metadata - headers & trailers ](https://github.com/google/grpc-java/blob/master/core/src/main/java/io/grpc/Metadata.java )
* [Status - error code namespace & handling ](https://github.com/google/grpc-java/blob/master/core/src/main/java/io/grpc/Status.java )
2014-12-16 02:24:42 +08:00
#### Client
2015-01-28 02:25:39 +08:00
* [Channel - client side binding ](https://github.com/google/grpc-java/blob/master/core/src/main/java/io/grpc/Channel.java )
2015-06-05 07:39:25 +08:00
* [Client Call ](https://github.com/google/grpc-java/blob/master/core/src/main/java/io/grpc/ClientCall.java )
2015-01-28 02:25:39 +08:00
* [Client Interceptor ](https://github.com/google/grpc-java/blob/master/core/src/main/java/io/grpc/ClientInterceptor.java )
2014-12-16 02:24:42 +08:00
#### Server
2015-01-28 02:25:39 +08:00
* [Server call handler - analog to Channel on server ](https://github.com/google/grpc-java/blob/master/core/src/main/java/io/grpc/ServerCallHandler.java )
* [Server Call ](https://github.com/google/grpc-java/blob/master/core/src/main/java/io/grpc/ServerCall.java )
2014-12-16 02:24:42 +08:00
2015-01-30 07:00:58 +08:00
### Transport
2014-12-16 02:24:42 +08:00
2015-08-08 14:28:06 +08:00
The Transport layer does the heavy lifting of putting and taking bytes off the
2015-08-06 07:48:15 +08:00
wire. The interfaces to it are abstract just enough to allow plugging in of
different implementations. Transports are modeled as `Stream` factories. The
variation in interface between a server Stream and a client Stream exists to
codify their differing semantics for cancellation and error reporting.
Note the transport layer API is considered internal to gRPC and has weaker API
guarantees than the core API under package `io.grpc` .
2015-08-08 14:28:06 +08:00
gRPC comes with three Transport implementations:
2015-08-06 07:48:15 +08:00
1. The [Netty-based ](https://github.com/google/grpc-java/blob/master/netty )
transport is the main transport implementation based on
[Netty ](http://netty.io ). It is for both the client and the server.
2. The [OkHttp-based ](https://github.com/google/grpc-java/blob/master/okhttp )
transport is a lightweight transport based on
[OkHttp ](http://square.github.io/okhttp/ ). It is mainly for use on Android
2015-08-08 14:28:06 +08:00
and is for client only.
2015-08-06 07:48:15 +08:00
3. The
2015-08-12 02:17:39 +08:00
[inProcess ](https://github.com/google/grpc-java/blob/master/core/src/main/java/io/grpc/inprocess )
2015-08-06 07:48:15 +08:00
transport is for when a server is in the same process as the client. It is
useful for testing.
2014-12-16 02:24:42 +08:00
#### Common
2015-08-12 02:17:39 +08:00
* [Stream ](https://github.com/google/grpc-java/blob/master/core/src/main/java/io/grpc/internal/Stream.java )
* [Stream Listener ](https://github.com/google/grpc-java/blob/master/core/src/main/java/io/grpc/internal/StreamListener.java )
2014-12-16 02:24:42 +08:00
#### Client
2015-08-12 02:17:39 +08:00
* [Client Stream ](https://github.com/google/grpc-java/blob/master/core/src/main/java/io/grpc/internal/ClientStream.java )
* [Client Stream Listener ](https://github.com/google/grpc-java/blob/master/core/src/main/java/io/grpc/internal/ClientStreamListener.java )
2014-12-16 02:24:42 +08:00
#### Server
2015-08-12 02:17:39 +08:00
* [Server Stream ](https://github.com/google/grpc-java/blob/master/core/src/main/java/io/grpc/internal/ServerStream.java )
* [Server Stream Listener ](https://github.com/google/grpc-java/blob/master/core/src/main/java/io/grpc/internal/ServerStreamListener.java )
2014-12-16 02:24:42 +08:00
2015-01-30 07:00:58 +08:00
### Examples
2014-12-16 02:24:42 +08:00
2015-08-06 07:48:15 +08:00
Tests showing how these layers are composed to execute calls using protobuf
messages can be found here
https://github.com/google/grpc-java/tree/master/interop-testing/src/main/java/io/grpc/testing/integration