Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 25266200C5A for ; Tue, 18 Apr 2017 23:51:46 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 2387A160BA1; Tue, 18 Apr 2017 21:51:46 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 67EFB160B87 for ; Tue, 18 Apr 2017 23:51:45 +0200 (CEST) Received: (qmail 29772 invoked by uid 500); 18 Apr 2017 21:51:44 -0000 Mailing-List: contact dev-help@geode.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@geode.apache.org Delivered-To: mailing list dev@geode.apache.org Received: (qmail 29760 invoked by uid 99); 18 Apr 2017 21:51:44 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Apr 2017 21:51:44 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 34AF0CD3CA for ; Tue, 18 Apr 2017 21:51:44 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id q5JPA6D_IUdb for ; Tue, 18 Apr 2017 21:51:43 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id BDF5B5FDCB for ; Tue, 18 Apr 2017 21:51:42 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 19CA4E081A for ; Tue, 18 Apr 2017 21:51:42 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id C3A5421B47 for ; Tue, 18 Apr 2017 21:51:41 +0000 (UTC) Date: Tue, 18 Apr 2017 21:51:41 +0000 (UTC) From: "Brian Baynes (JIRA)" To: dev@geode.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (GEODE-2746) Investigate and Evaluate Existing RPC frameworks. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 18 Apr 2017 21:51:46 -0000 [ https://issues.apache.org/jira/browse/GEODE-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Baynes resolved GEODE-2746. --------------------------------- Resolution: Duplicate Superseded by GEODE-2781/2782/2783 > 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 > Assignee: 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)