| commit | b1cc7cc09d485851028868f073db825bf11937a3 | [log] [tgz] |
|---|---|---|
| author | Jeff Pinner <jpinner@twitter.com> | Wed Feb 25 10:17:23 2015 -0800 |
| committer | Jeff Pinner <jpinner@twitter.com> | Wed Feb 25 10:17:23 2015 -0800 |
| tree | 6ef02fdb49e32017dfc246de0379e878188c9180 | |
| parent | 488f8a99893c14ba9806a335ec73bffe11937d26 [diff] |
Upgrade com.twitter.hpack to v0.10.1
grpc-java requires Netty 5, which is still in flux. The version we need can be found in the lib/netty submodule, which requires Maven 3.2 or higher to build:
$ git submodule update --init $ cd lib/netty $ mvn install -pl codec-http2 -am -DskipTests=true
The codegen plugin requires a recent protobuf build from master (what will become proto3):
$ git clone https://github.com/google/protobuf.git $ cd protobuf $ ./autogen.sh $ ./configure $ make $ make check $ sudo make install $ cd java $ mvn install
If you are comfortable with C++ compilation and autotools, you can specify a --prefix for protobuf and use -I in CXXFLAGS, -L in LDFLAGS, LD_LIBRARY_PATH, and PATH to reference it. The environment variables will be used when building grpc-java.
Protobuf installs to /usr/local by default. If /usr/local/lib is not in your library search path, you can add it by running:
$ sudo sh -c 'echo /usr/local/lib >> /etc/ld.so.conf' $ sudo ldconfig
Now to build grpc-java itself:
$ ./gradlew install
Heres 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. An example is provided of a binding to code generated by the protocol-buffers compiler but others 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 & 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.
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/integration-testing/src/main/java/io/grpc/testing/integration