commit | b1d91b9f60c33019ffe36073b4b2a4dbbe95ec67 | [log] [tgz] |
---|---|---|
author | zpencer <spencerfang@google.com> | Tue Apr 03 13:39:11 2018 -0700 |
committer | GitHub <noreply@github.com> | Tue Apr 03 13:39:11 2018 -0700 |
tree | c2fd58a380695f2055f4dd48c72249388e0c77f6 | |
parent | 724e32fe57db8ba21a180632cb144d5af0a814c4 [diff] |
core,services: binary log should use real peer socket and call id (#4266) The peer socket is read from TRANSPORT_ATTR_REMOTE_ADDR from the stream attributes. We only log the peer on receive initial metadata. The call id assumes census is available. The call ID read from the context via SERVER_CALL_ID_CONTEXT_KEY on server side, and read from CallOptions via CLIENT_CALL_ID_CALLOPTION_KEY on client side. The value is copied from CONTEXT_SPAN_KEY which is set by census. Pass around CallId with two longs, not a byte[].
gRPC-Java works with JDK 6. On Android, gRPC-Java supports Android API levels 14 and up (Ice Cream Sandwich and later).
TLS usage typically requires using Java 8, or Play Services Dynamic Security Provider on Android. Please see the Security Readme.
Download the JARs. Or for Maven with non-Android, add to your pom.xml
:
<dependency> <groupId>io.grpc</groupId> <artifactId>grpc-netty</artifactId> <version>1.11.0</version> </dependency> <dependency> <groupId>io.grpc</groupId> <artifactId>grpc-protobuf</artifactId> <version>1.11.0</version> </dependency> <dependency> <groupId>io.grpc</groupId> <artifactId>grpc-stub</artifactId> <version>1.11.0</version> </dependency>
Or for Gradle with non-Android, add to your dependencies:
compile 'io.grpc:grpc-netty:1.11.0' compile 'io.grpc:grpc-protobuf:1.11.0' compile 'io.grpc:grpc-stub:1.11.0'
For Android client, use grpc-okhttp
instead of grpc-netty
and grpc-protobuf-lite
or grpc-protobuf-nano
instead of grpc-protobuf
:
compile 'io.grpc:grpc-okhttp:1.11.0' compile 'io.grpc:grpc-protobuf-lite:1.11.0' compile 'io.grpc:grpc-stub:1.11.0'
Development snapshots are available in Sonatypes's snapshot repository.
For protobuf-based codegen, you can put your proto files in the src/main/proto
and src/test/proto
directories along with an appropriate plugin.
For protobuf-based codegen integrated with the Maven build system, you can use protobuf-maven-plugin (Eclipse and NetBeans users should also look at os-maven-plugin
's IDE documentation):
<build> <extensions> <extension> <groupId>kr.motd.maven</groupId> <artifactId>os-maven-plugin</artifactId> <version>1.5.0.Final</version> </extension> </extensions> <plugins> <plugin> <groupId>org.xolstice.maven.plugins</groupId> <artifactId>protobuf-maven-plugin</artifactId> <version>0.5.0</version> <configuration> <protocArtifact>com.google.protobuf:protoc:3.5.1-1:exe:${os.detected.classifier}</protocArtifact> <pluginId>grpc-java</pluginId> <pluginArtifact>io.grpc:protoc-gen-grpc-java:1.11.0:exe:${os.detected.classifier}</pluginArtifact> </configuration> <executions> <execution> <goals> <goal>compile</goal> <goal>compile-custom</goal> </goals> </execution> </executions> </plugin> </plugins> </build>
For protobuf-based codegen integrated with the Gradle build system, you can use protobuf-gradle-plugin:
apply plugin: 'java' apply plugin: 'com.google.protobuf' buildscript { repositories { mavenCentral() } dependencies { // ASSUMES GRADLE 2.12 OR HIGHER. Use plugin version 0.7.5 with earlier // gradle versions classpath 'com.google.protobuf:protobuf-gradle-plugin:0.8.3' } } protobuf { protoc { artifact = "com.google.protobuf:protoc:3.5.1-1" } plugins { grpc { artifact = 'io.grpc:protoc-gen-grpc-java:1.11.0' } } generateProtoTasks { all()*.plugins { grpc {} } } }
If you are making changes to gRPC-Java, see the compiling instructions.
Here's a quick readers' guide to the code to help folks get started. At a high level there are three distinct layers to the library: Stub, Channel & Transport.
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 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.
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.
The Transport layer does the heavy lifting of putting and taking bytes off the 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
.
gRPC comes with three Transport implementations:
The examples and the Android example are standalone projects that showcase the usage of gRPC.
APIs annotated with @Internal
are for internal use by the gRPC library and should not be used by gRPC users. APIs annotated with @ExperimentalApi
are subject to change in future releases, and library code that other projects may depend on should not use these APIs. We recommend using the grpc-java-api-checker (an Error Prone plugin) to check for usages of @ExperimentalApi
and @Internal
in any library code that depends on gRPC. It may also be used to check for @Internal
usage or unintended @ExperimentalApi
consumption in non-library code.