From 3e366732f47c850dd9734dfabfada204e9bef7be Mon Sep 17 00:00:00 2001 From: Paul Grosu Date: Tue, 6 Dec 2016 22:28:38 -0500 Subject: submit --- chapter/1/gRPC.md | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) (limited to 'chapter/1') diff --git a/chapter/1/gRPC.md b/chapter/1/gRPC.md index 08962b1..7d9cd34 100644 --- a/chapter/1/gRPC.md +++ b/chapter/1/gRPC.md @@ -167,12 +167,9 @@ Most of these will require tweaking the Protobuf file and testing the throughput One starts by initializing a communication Channel between Client to a Server and storing that as a Stub. The Credentials are provided to the Channel when being initialized. These form a Context for the Client's connection to the Server. Then a Request can be built based on the definition in the Protobuf file. The Request and associated expectedResponse is executed by the service constructed in the Protobuf file. The Response is them parsed for any data coming from the Channel. -The connection can be asynchronous and bi-directionally streaming so that data is constantly flowing back and available to be read when ready. This allows one to treat the Client and Server as endpoints where one can even adjust not just the flow but also intercept to filter and thus request the data of interest. +The connection can be asynchronous and bi-directionally streaming so that data is constantly flowing back and available to be read when ready. This allows one to treat the Client and Server as endpoints where one can even adjust not just the flow but also intercept and decoration to filter and thus request and retrieve the data of interest. -That stub can be referenced later in order - - -The Java implementation of gRPC been built with Mobile platform in mind and to +The Transport Layer performs the retrieval and placing of binary protocol on the wire. For gRPC-Java has three implementations, though a user can implement their own: Netty, OkHttp, and inProcess.

3... gRPC Java

-- cgit v1.2.3