Return-Path: X-Original-To: apmail-avro-dev-archive@www.apache.org Delivered-To: apmail-avro-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8DB3218582 for ; Sun, 10 Jan 2016 22:11:40 +0000 (UTC) Received: (qmail 36433 invoked by uid 500); 10 Jan 2016 22:11:40 -0000 Delivered-To: apmail-avro-dev-archive@avro.apache.org Received: (qmail 36334 invoked by uid 500); 10 Jan 2016 22:11:40 -0000 Mailing-List: contact dev-help@avro.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@avro.apache.org Delivered-To: mailing list dev@avro.apache.org Received: (qmail 36007 invoked by uid 99); 10 Jan 2016 22:11:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 10 Jan 2016 22:11:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id D34552C1F5C for ; Sun, 10 Jan 2016 22:11:39 +0000 (UTC) Date: Sun, 10 Jan 2016 22:11:39 +0000 (UTC) From: "Matthieu Monsch (JIRA)" To: dev@avro.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AVRO-1778) IPC/RPC for JavaScript MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AVRO-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthieu Monsch updated AVRO-1778: ---------------------------------- Assignee: Ryan Blue > IPC/RPC for JavaScript > ---------------------- > > Key: AVRO-1778 > URL: https://issues.apache.org/jira/browse/AVRO-1778 > Project: Avro > Issue Type: Improvement > Components: javascript > Reporter: Matthieu Monsch > Assignee: Ryan Blue > > This patch adds protocols to the JavaScript implementation. > The API was designed to: > + Be simple and idiomatic. The `Protocol` class added here is heavily inspired by node.js' core `EventEmitter` to keep things as familiar as possible [1]. Getting a client and server working is straightforward and requires very few lines of code [2]. > + Support arbitrary transports, both stateful and stateless. Communication over built-in node.js streams are supported out of the box (e.g. TCP/UNIX sockets, or even stdin/stdout). Exchanging messages over a custom transport requires implementing a single simple function (see [3] for an example). > + Work both server-side and in the browser (!). > Ps: I also tested against both the Java and Python implementations over HTTP and communication worked. > [1] https://github.com/mtth/avsc/wiki/API#ipc--rpc > [2] https://github.com/mtth/avsc/wiki/Advanced-usage#remote-procedure-calls > [3] https://github.com/mtth/avsc/wiki/Advanced-usage#transient-streams -- This message was sent by Atlassian JIRA (v6.3.4#6332)