Note that finagle is not thrift specific. It's rpc protocol agnostic.
We can make a finagle-hadooprpc connector. Granted, the thrift
implementation is pretty hardened. Actually the fact that finagle is
independent of rpc frework may be another reason to use it -- flip
between hadooprpc and thrift depending on whether you want performance
or security.

On Sep 18, 2011, at 8:08 AM, "Jakob Homan (JIRA)" <j...@apache.org> wrote:

>
>    [ 
> https://issues.apache.org/jira/browse/GIRAPH-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13107455#comment-13107455
>  ]
>
> Jakob Homan commented on GIRAPH-37:
> -----------------------------------
>
> I'll take a look at Finagle.  Security probably won't be in the first 
> version, but as a veteran of the Hadoop Security Wars myself, I'll be sure it 
> can be supported.
>
>> Implement Netty-backed rpc solution
>> -----------------------------------
>>
>>                Key: GIRAPH-37
>>                URL: https://issues.apache.org/jira/browse/GIRAPH-37
>>            Project: Giraph
>>         Issue Type: New Feature
>>           Reporter: Jakob Homan
>>           Assignee: Jakob Homan
>>
>> GIRAPH-12 considered replacing the current Hadoop based rpc method with 
>> Netty, but didn't went in another direction. I think there is still value in 
>> this approach, and will also look at Finagle.
>
> --
> This message is automatically generated by JIRA.
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>

Reply via email to