Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Fri, 17 Jun 2011 21:33:48 +0000 (UTC)
From: "Jitendra Nath Pandey (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <1503965830.16584.1308346428064.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1593248389.10179.1308212149301.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HADOOP-7399) Remove Writable from ipc.Client and
 ipc.Server.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HADOOP-7399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jitendra Nath Pandey updated HADOOP-7399:
-----------------------------------------

    Attachment: HADOOP-7399.3.patch

This is a very early version of the patch. I still need to do lot more code cleanup. Sasl messages for connection setup also need to be handled consistently. The basic idea is to use ClientCall and ServerCall as the abstractions for interaction between an RpcEngine and ipc.Client/Server.

> Remove Writable from ipc.Client and ipc.Server.
> -----------------------------------------------
>
>                 Key: HADOOP-7399
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7399
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Jitendra Nath Pandey
>            Assignee: Jitendra Nath Pandey
>         Attachments: HADOOP-7399.3.patch
>
>
>   This jira proposes to remove the dependency of ipc client and server on Writable. I think this will be an important step towards making an RpcEngine truly configurable, without having to use tunnel protocols as in case of AvroRPCEngine.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira