[
https://issues.apache.org/jira/browse/GEODE-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15967922#comment-15967922
]
Avinash Dongre commented on GEODE-2746:
---------------------------------------
When I was trying out gRPC, I also faced the same problem. One need to use
ServerCallStreamObserver and ServerCallStreamObserver.setOnReadyHandler, when
you have lot of message in case of stream. (
https://github.com/davinash/grpc-bench)
> Investigate and Evaluate Existing RPC frameworks.
> -------------------------------------------------
>
> Key: GEODE-2746
> URL: https://issues.apache.org/jira/browse/GEODE-2746
> Project: Geode
> Issue Type: Sub-task
> Components: messaging
> Reporter: Galen O'Sullivan
>
> There are several existing RPC frameworks for which you can define the
> structure of your protocol and the tool will generate code for talking over
> the wire, generally down to serialization of objects.
> If one of those RPC frameworks does not fit all our requirements, we'll
> design our own binary protocol. This protocol would define both what kind of
> messages can be sent and how they are encoded on the wire. How we encode the
> objects that we are sending in requests, however, could still be pluggable.
> A few contenders:
> * [BERT|http://bert-rpc.org]
> * [thrift|https://thrift.apache.org/]
> * [gRPC|http://www.grpc.io/]
> * [Avro|https://avro.apache.org/]
> These are two not-entirely-common features we will need to have:
> * support for SSL/TLS, ability to connect to a server with IP & port.
> * support for push messages from the server without polling (this is needed
> for CQs).
> This is one half of GEODE-2734.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
