| commit | 11c363a7ae5d9974f052423e46ef0daaacaaf20a | [log] [tgz] |
|---|---|---|
| author | nathanmittler <nathanmittler@google.com> | Fri Jan 09 11:22:19 2015 -0800 |
| committer | Eric Anderson <ejona@google.com> | Fri Jan 09 17:00:25 2015 -0800 |
| tree | 13030ab0fc6fd92c6e0258bbc018fb2bf4e713a9 | |
| parent | f8524a17b80a3830775257b68e14a692f2e96a93 [diff] |
Disallowing message delivery after status has been delivered to the listener. Summary of changes: 1) Merged the interfaces MessageDeframer2.Sink and DeframerListener into MessageDeframer2.Listener. This simplifies the interface of MessageDeframer2 quite a bit. 2) Added a deliveryPaused() handler to MessageDeframer2.Listener, which is called by the deframer when there is not enough data to read/deliver the next message. 3) Modified AbstractStream and AbstractClientStream to manage the timing of when the closed() event is delivered to the listener. The transportReportStatus ultimately controls this by creating a task to close the listener. It either runs this task immediately or when the next deliveryPaused() event occurs. ------------- Created by MOE: http://code.google.com/p/moe-java MOE_MIGRATED_REVID=83620903
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/com/google/net/stubby/testing/integration